Front client foundation / July 29, 2026English-first premium lifestyle publication
4launch territories: fashion, beauty, travel and lifestyle. 6reusable page-builder sections already wired into the new front. PrivateCMS administration remains separated from the public surface.
The Glorioous homepage now reads like a private edit, not a placeholder.
This first client-facing foundation keeps the Glorioous brand direction and adopts the architecture we wanted: shared layout, composable sections, page-level SEO, preview compatibility and a cleaner editorial rhythm.
Edition frame
The recommended front template is now visible in the page structure itself.
We are not waiting for the full Strapi page-builder model to improve the front. The public site already adopts the right rendering grammar, which makes the future CMS connection much less risky.
One shell for the whole publication
Header, footer, metadata and structured data are centralized instead of duplicated across standalone HTML files.
- Route-aware navigation
- Shared brand lockup and issue label
- Consistent canonical strategy
Pages are assembled from sections, not hardcoded slabs
Each page now resolves through a section registry inspired by the target Notum structure, making future CMS composition a direct continuation rather than a rewrite.
- Hero renderer
- Editorial card grids
- Features and process rails
Next.js standalone replaces the old static nginx bundle
The runtime now matches the public-front ambition: health route, preview entrypoint and revalidation hook included.
- App Router structure
- Standalone container output
- Infra port shift to 3000
Editorial territories
Four launch territories, one composed publishing voice.
The categories stay clear, but the page avoids the generic magazine-demo feeling. Each territory is framed like a confident editorial lane rather than a noisy content bucket.
Trend language that still respects a real wardrobe.
Silhouette, fabric, cut and staying power matter more than hype cycles.
Routines and textures with stronger buying logic.
The beauty voice stays selective, tactile and useful instead of over-claiming novelty.
Escapes selected for atmosphere, pace and credibility.
Destinations should feel editorially specific, not like recycled lifestyle filler.
Objects, rituals and gifting with composure.
The lifestyle lane sharpens everyday decisions without flattening taste into templates.
What the foundation does now
The page is no longer a placeholder front.
This release is intentionally narrow, but it already resolves the main concern: the live site now follows the client-front architecture we chose, even if the Strapi content model is not fully ready yet.
Generic route, shared page definitions
The front resolves pages through a central page catalog and a single route entrypoint rather than separate static documents.
Preview and revalidation compatibility
The endpoint contract exists now, so wiring future Strapi publish flows becomes incremental work instead of a ground-up runtime swap.
Safer future CMS migration
When `Page`, `Navbar` and `Footer` arrive in Strapi, we can swap the data source while keeping most of the rendering surface intact.
Operator chain
The gloss is public. The machinery stays disciplined.
The public front can look more finished without exposing internal admin surfaces or collapsing the separation between editorial source of truth, production and publication.
Directus remains the editorial source of truth
Planning, briefs, taxonomies and governance still belong to the upstream operator layer.
FORGE stays the production layer
Transformation and packaging stay outside the public front and outside public CMS access.
Strapi remains the publication runtime
The admin endpoint stays private while the public API surface will expand only when the editorial model is ready.
Glorioous front renders the client edition
The public site now owns presentation, metadata and composable page sections without impersonating the private back office.