Why we build marketing sites with Astro
Your marketing site’s job is SEO and first paint. Here’s why we ship them as static Astro sites with small interactive islands - even when the product itself is a Vue app.
Invoke Technologies · · 1 min read
When a product team already has a single-page app, the obvious move is to build the marketing site the same way. We usually don’t - and this site is a good example of why.
A marketing site has a different job
A dashboard’s job is interactivity. A marketing site’s job is to load instantly, rank well, and convert. Those goals favor plain, pre-rendered HTML over a JavaScript bundle that has to download and execute before anything appears.
Astro gives you both
Astro renders pages to static HTML at build time. When a page genuinely needs interactivity - a mobile menu, a pricing calculator, a contact form - you drop in a component from a framework you already use, like Vue, and Astro hydrates only that “island.” Everything else ships as zero-JavaScript HTML.
What we include by default
- Content collections in Markdown with typed, validated frontmatter - so blog posts and landing pages don’t need a developer.
- Structured data (Organization, Article, FAQPage) and a generated sitemap.
- Social share cards generated from code, so they stay on-brand.
- Shared design tokens with the product UI, so the site and app look like one brand.
- Type checking in the build, so a broken link or bad frontmatter fails before it ships.
Same repo, separate deploy
For product companies, we often keep the marketing site in the same repository as the app. One pull request can ship a feature and the page announcing it - but the site still deploys independently as static files to any CDN.
If your site is slow, hard to update, or doesn’t match your product, we can help. See our marketing site services.