Why v1.0

经过前期多个版本的底层验证与打磨，v1.0 标志着平台正式迈入高可用、高度纯净的生产级运行阶段。

本版本核心聚焦于架构一致性、独立资产系统与全链路 SEO 优化。

What changed

独立品牌与系统纯净化

• 完成 100% 独立且现代化的品牌资产与规范化 URL 重构
• 根除所有冗余外部暗桩与第三方追踪，代码层实现彻底纯净化
• 统一元数据结构，深度集成 Schema.org 结构化数据与绝对化 Canonical 链接

Page and route coverage

• Added static auth templates for /sign-in and /sign-up
• Refreshed the 404 page with clearer recovery actions and a stronger visual state
• Completed Header and Footer links for Sign in, Sign up, and 404
• Kept core marketing pages, auth templates, content pages, and utility pages wired through the same layout system

Content polish

• Reframed the release history as v0.1, v0.2, v0.3, and final v1.0
• Reworked sample blog posts so they read like production-ready English content, not placeholder copy
• Preserved the verified Lighthouse 95+ claim across Performance, Accessibility, Best Practices, and SEO
• Removed stale roadmap language that implied newer post-1.0 versions already existed

Compatibility

• No new runtime dependency is required for the stable content set
• Existing forks can keep their page structure and update content incrementally
• Teams upgrading from an earlier preview should review src/config/site.js, src/styles/global.css, and src/content/

Upgrade notes

If you forked a v0.x preview:

1. Run pnpm install
2. Review src/content/post/ and src/content/changelog/ for the new release story
3. Update any custom links pointing to /blog/launching-v1-2; the stable release article now lives at /blog/launching-v1-0
4. Re-check your own copy against the final v1.0 page set

v1.0 是坚实且完备的长期支持版本。

Migration to Content Layer

Blog and changelog content moved to Astro’s glob loader and Content Layer API. The migration removed older content patterns and made the site easier to extend later with external Markdown, a CMS, or another content source.

Key changes from the earlier preview:

• entry.slug became entry.id
• entry.render() became render(entry) from astro:content
• Astro.glob() usage moved to import.meta.glob() where static imports were still needed
• getStaticPaths() params were normalized for Astro v6 readiness

Schema unification

Blog and changelog frontmatter now follow a shared shape:

title: string
description: string
publishDate: date
version?: string     # changelog only
tags?: string[]      # blog only
read?: number        # blog only
img?: string
img_alt?: string
featured?: boolean

Performance wins

• Cold build time: 21s -> 14s on CI (Vercel hobby runner, 8 routes)
• First-load JS on Home: 31KB -> 24KB gzipped after splitting AnimatedText into a dynamic chunk
• Blog cards now use loading="lazy" by default
• Lighthouse on a fresh install: 95+ across Performance, Accessibility, Best Practices, and SEO on Home, Features, and Pricing

Release status

v0.3 locked the content and performance baseline. The remaining work before v1.0 was product-story polish, route coverage, and final template cleanup.

Improvements

• Dark mode contrast pass - lifted --color-text-secondary-dark from #a8b5c8 to #c5cedb for better body-copy readability at 14-16px sizes
• Primary in dark mode - brightened --color-primary-dark from #3478d4 to #3884eb so links stay readable against the deep navy canvas
• Softer card edges - dark-mode card borders moved from neutral-800 to neutral-700
• AnimatedText tuning - tightened the hero text entrance timing and reduced first-paint overhead
• AOS staggering - standardized reveal sequences around predictable delay steps

New component

• BrowserFrame.astro - the Mac-style window chrome around product previews, extracted into a reusable component with url, variant, and className props

Fixes

• Header z-index conflict with FAQ accordion on mobile Safari
• prefers-reduced-motion handling for text entrances
• TOC sticky offset on wide article layouts

Release status

v0.2 made the template feel more coherent, but the content architecture and final SaaS story were still being shaped for v1.0.

What’s included

• Core marketing pages for Home, Features, Pricing, Blog, Changelog, About, Contact, Elements, and 404
• A reusable section system for hero areas, feature blocks, pricing cards, comparison tables, FAQ, tech stack, use cases, and final CTAs
• MDX-powered blog with featured posts, pagination, tags, reading progress, and table of contents
• Changelog timeline with version badges and MDX content support
• Built-in dark mode with no flash on load
• Responsive layouts across phone, tablet, laptop, and desktop breakpoints
• AOS scroll reveals with small custom presets
• Animated hero text entrance with staggered timing
• Pricing toggle for monthly and yearly billing examples
• Accordion items for FAQ sections
• Badge component with primary, accent, success, info, warning, and danger variants
• SEO-ready metadata, Open Graph tags, sitemap, and RSS feed
• Elements reference page for checking tokens, components, and UI states

Why it stayed pre-1.0

This release proved the shape of the template, but the content model and visual story still needed refinement. We kept it in the v0.x line so teams could test the foundation without treating the public API as final.