Premium homepage kit
Reusable homepage sections for polished client prototypes without dragging in page-builder complexity.
The shared library now covers the core homepage arc: hero, proof, value grid, split feature story, stat band, and closing CTA, all driven by typed site configs.
- Homepage-focused abstractions instead of CMS-generalized schema
- Shared shell and section primitives that skin cleanly per site
- Defaults polished enough for authority and hospitality directions
- Typed section config keeps iteration fast and low-risk
Included patterns
Six reusable section types
Enough structure for premium demo work while keeping per-site content simple to author and maintain.
Shell primitives
Header + footer
Section patterns
Hero to CTA
Theme skins
default / cgtf / vpg
Workflow
Local-only
Designed for shared reuse
Authority-ready
Supports more executive, outcome-led messaging for CGTF.
Experience-led
Adapts to the warmer golf and hospitality tone needed by VPG.
Composed in code
Simple typed config replaces hard-to-maintain visual builder logic.
Fast to iterate
Swap section content and theme tokens without touching the render path.
Shared homepage library
Reusable section building blocks with sensible defaults already baked in.
Each pattern is opinionated enough to look premium quickly, but still flexible enough for real client variation.
Hero
Lead with positioning and a proof panel
Headline, supporting copy, CTA pair, trust bullets, and a featured summary block establish the offer fast.
Proof
Trust strip for credibility without overcomplication
A compact band surfaces recognizers, differentiators, or signature promises near the top of the page.
Value grid
Card grid for service pillars or strategic benefits
Flexible cards support authority-style frameworks, resort experience pillars, or engine capability summaries.
Story section
Split feature for narrative plus supporting evidence
Text, bullets, CTAs, stat tiles, and a quote-like detail create a premium mid-page anchor.
Momentum
Stat band for quantified outcomes or operating signals
Use concise performance numbers, rollout readiness indicators, or high-level proof points.
Conversion
CTA band to close the page with intent
A high-contrast band keeps the final ask visible without needing a bespoke section every time.
Flexible section composition
One shared section system now supports very different homepage directions.
CGTF can lean harder into authority, strategic clarity, and executive proof. VPG can shift toward destination energy, hospitality cues, and experience-forward storytelling.
The common renderer stays practical because it focuses on the patterns both prototypes actually need, rather than abstracting into a page-builder or CMS framework.
- Shared container, panel, heading, and button helpers keep visual quality consistent.
- Section-level defaults reduce duplicated layout work when spinning up new homepage concepts.
- Typed content models stay readable inside each site config instead of drifting into generic JSON blobs.
Why this stays practical
Homepage-focused abstractions, not a generalized content system.
Every section exists because it is immediately useful to the current prototype shell and the two planned site variants.
Section types
6
Shared skins
3
Remote dependencies
0
Setup friction
Low
“Build the common arc once, then let each site config sharpen the tone and offer.”
Readiness
The shared homepage layer is now substantial enough to support both prototype tracks.
Core section coverage is in place, the shell is reusable, and each profile can now focus on market-specific content and visual direction.
Ready
Shared shell
Header and footer primitives support the current local shell.
Complete
Homepage arc
Hero, proof, grid, split feature, stats, and CTA all ship together.
3
Site skins
default, cgtf, and vpg all render from the same component library.
Avoided
Generalization
Models stay scoped to homepage prototype needs.
Next move
Use the shared library to spin up sharper CGTF and VPG homepages faster.
The engine core is no longer the blocker. The next work can stay focused on copy, visuals, and per-site nuance instead of rebuilding layout primitives.
Local-only implementation. No remotes, deployment steps, or environment-specific live work were introduced.