Keep article previews consistent
One card pattern should handle guides, release notes, and case-study style content without page-specific wrappers.
Resources
Blog and implementation notes
Use the shared article contracts for guides, updates, and case studies so the resource surface stays as calm and reusable as the homepage and pricing routes.
Editorial system
Resource routes should still support product discovery.
The blog is more than a list of posts. It should explain implementation choices, capture release context, and gently route readers toward docs, pricing, or contact without changing the visual language.
Cross-link the rest of the surface
Resource pages should naturally point into docs, changelog, about, pricing, and contact instead of becoming a dead-end content bucket.
Latest posts
One resource pattern, multiple editorial jobs.
These cards show how the same layout can cover long-form guidance, operational notes, supporting references, and route-level cross-links.
How to rebrand the starter without layout drift
A practical walkthrough of tokens, semantic contracts, and page composition boundaries.
Read articleWhat changed in the marketing system
Summarize release notes and route-level progress with a structure that matches the rest of the public surface.
Open changelogScaling one framework across multiple clients
Show how teams can reuse the shell while still producing differentiated public-facing experiences.
About the teamWhy the homepage is the design reference route
Capture the preferred hero, proof, FAQ, and CTA rhythm so new marketing pages can extend instead of improvise.
Review homepageWhere to verify the shared section contracts
Use the docs route to confirm component behavior and section rules before adding deeper route-level composition.
Open docsWhen editorial content should hand off to sales
Keep the resource layer useful, but make the next high-intent path to pricing or contact obvious.
Talk to the team Next step
Move from reading to implementation.
Pair editorial content with one clear action so the resource layer still supports product discovery and conversion.