​

Blog redesign — review and QA

Reference: https://silvia-staging.framer.website/blog and /blog/demo. Branch: codex/blog-page-redesign, originally based on staging a6aa421 and refreshed against staging before opening the PR. The directory and articles match the reference’s dark editorial layout with real Sanity content. Navigation and footer reuse the unchanged V5 landing components. The blog-owned final signup section reuses the unchanged landing section container and design tokens, with its own copy and attribution. It therefore follows the implemented landing design rather than the Framer demo’s different mockup. Author metadata, TOC, FAQ and financial notice are retained for existing long-form articles. No Sanity documents, schemas or releases were modified. The frontend PR targets staging. The final scope review restores all shared landing source files to staging, so other application pages and the landing experiment are unchanged. The only package-manifest addition is the development dependency needed for the blog’s related-post query tests.

​

Silvia navigation knowledge

The current CFO-Silvia/skills/silvia-navigation-skills/SKILL.md was inspected. It does not currently document the public blog. A companion navigation update has been prepared on codex/blog-redesign-navigation in the local skills checkout. Publishing it is blocked: the authenticated GitHub account has read-only access to CFO-Silvia/skills, and that repository disables forking. A maintainer must open the companion PR before shipping. The update covers:

The public blog is at /blog (“Silvia news and insights”). Select a category pill to filter posts, or choose “All” to clear the category. Enter a query in Search and press Enter; use Clear search to remove it. Previous / Next navigate the archive while keeping filters. Open a card to read an article; “Back to blog” returns to the directory. Articles may include an “On this page” table of contents, FAQ and Related posts. Share controls open a social composer or copy the article URL; users choose whether to publish. LinkedIn and X icons beside an author open the profiles saved in Sanity.

A companion PR should target staging and follow the skills repository’s current README: a later authorized staging merge automatically syncs to silvia-skills-dev. No merge or manual S3 deployment has been performed.

​

Validation

• 129 focused tests passed across 22 blog, routing/metadata and Sanity suites.
• ESLint passed the blog routes, components and helpers; the full repository TypeScript check passed after refreshing the branch from staging.
• Read-only Sanity verification on September 25 covered 80 published posts, eight categories and four authors. Required fields and references are valid; all hero assets load. The live listing, search, detail and related queries return the expected content, with 80 unique posts across ten archive pages.
• Browser-checked desktop and 390px mobile layouts with live published Sanity data: category selection, category-preserving search, page 2, empty search, article navigation, author metadata, images and related cards. No horizontal page overflow was observed.
• Local verification uses a clean lockfile dependency install. groq-js is explicitly declared as a development dependency for the query tests, pinned to the version already in the lockfile. A full local production build is not covered because unrelated application routes need service credentials absent locally. The PR’s configured CI/preview build is the full-build gate.
• The local preview has no configured development Clerk or Supabase account; authentication/status integrations are not part of this visual check. The blog itself reads the public Sanity production dataset without a token.