Built for fast client delivery
Typed config and reusable blocks make project bootstrapping quick without turning the template into a page builder.
Astro agency starter
Launch bespoke marketing sites fast without inheriting a CMS mess.
A static-first, content-friendly foundation for agency projects that need strong SEO, consent-safe tracking, and clean handoff paths.
90+
Lighthouse-friendly base
Static
Deploy model
MDX
Blog authoring
System
A clean delivery system for marketing websites.
Keep the shell reusable, the design flexible, and the content easy to manage.
SEO and content baked in
Meta tags, sitemap, robots, JSON-LD, and file-based blog workflows are ready from day one.
Consent-gated marketing stack
GTM, GA4, and Meta Pixel only load after the right cookie categories are accepted.
Easy to skin from Figma
CSS tokens and composable Astro sections keep redesign work focused and predictable.
Proof
A foundation built for repeatable delivery, not repeated rewrites.
Use it as a stable baseline across brochure sites, launch pages, and content-led company websites.
“The new site shipped in days, not weeks, and our lead quality improved immediately.”
Managing Director, Studio Forma
“Northstar gave us a clean system we can keep reusing for launches, campaigns, and case studies.”
Marketing Lead, Brightpath
“Fast, technically sound, and easy to extend when our backend requirements changed.”
Founder, Pulse Advisory
Questions teams ask before adopting the starter
The template stays intentionally narrow so agency delivery stays fast.
Is this a CMS?
No. It is a reusable marketing-site starter with file-based content, not a multi-tenant content platform.
Can we connect a custom backend later?
Yes. Forms already post to an external endpoint, and the structure is ready to consume a separate API when needed.
Does this support one-off custom design work?
Yes. The component and token layers are intended to be replaced or extended from Figma without rewriting the project core.
Ready to turn a design file into a launch-ready site?
Start with the baseline, replace the sections with your Figma-specific implementation, and keep the SEO and deployment layer intact.