-
Notifications
You must be signed in to change notification settings - Fork 0
V2 Launch
John authorized the final V2 release, launch announcement, master → main rename, repository/README/wiki updates, and sharing reminders. The launch article covers the design process, challenges, AI collaboration, staging, feature previews, CI, and the future.
- Native article: A new home for my work, writing, and curiosity.
- Split V1/V2 thumbnail and an unaltered V2 homepage screenshot.
- Launch placement on Home, Writing, and Blog.
- LinkedIn, Facebook, and Threads drafts in launch-social-posts.md.
- Reusable expandable AI-assistance disclosure pill.
- Existing About portrait used because Google Photos sign-in did not complete.
Site-wide static search covers pages, articles, projects, talks, and media. Production metadata, canonical URLs, robots, sitemap, and BlogPosting structured data are configured. Staging remains noindex, analytics-isolated, and independently deployed.
Source CI builds both production and staging. The generated-site checker validates internal pages, assets, downloads, fragments, launch placement, and metadata. Production and staging use separate consent-gated GA4 properties, and analytics coverage is loaded across the V2 layouts. Both READMEs document design authorship, AI assistance, technologies, and release flow.
Production publishes from main/root. Integration remains v2 and staging remains a separate repository with feature or pinned-ref selection.
The integration head used for the first promotion was 0affc08; it did not include the actual live feature-branch staging revision. PR #49 promoted v2 into main and merged as 5177c98 on October 2, 2026. Local production and staging safe Jekyll builds passed for 29 HTML pages and 722 internal links/assets/anchors. The staging privacy checker passed.
The previous local release validation also passed CI and live staging checks for the launch article, screenshot, AI disclosure, search, navigation, and downloads. The inherited local Ruby 3 compatibility shim was used locally; canonical CI uses Ruby 2.7/Bundler 2.4.22.
Physical Fold6/full accessibility verification, external-link maintenance, dependency modernization, broader toolbar refinement, monitoring/admin, and a later screenshot refresh remain separate follow-ups. V2 launch does not close those scopes.
Release guide. Previous V1 production commit: 51809fc5f070650bdb8c8d408b09278db1fa5743. Revert the release merge on main and verify Pages. Never deploy a staging artifact into production.
PR #50 promoted the actual live staging revision d2065ffc52b5345e00fb23a87c0fb22f330c842e into main as 1b136c4f72e09b9a7634b8bd393340c49bdb1338. It includes inline rollout search, narrow-screen navigation, Original/Dark/Darker appearance controls, and admin entry/dashboard source. The first promotion (#49) omitted these changes because staging was pinned to a feature revision rather than v2. Future release checks must compare live staging build-info.json with the source being promoted. Admin backend activation remains pending Cloudflare configuration.