Launch a fast Storyblok website without starting from zero.

A production-ready Next.js or Astro starter shaped by Makers Den for teams that care about performance, editorial control, and clean implementation.

Layered Makers Den website interface graphic

Choose the frontend that fits your project.

Next.js template

Use the Next.js starter when your team wants App Router, React Server Components, and familiar React hosting patterns on top of the shared Storyblok schema.

View Next.js README

Astro template

Use the Astro starter for content-heavy marketing sites that benefit from low client JavaScript, native Astro components, and Cloudflare deployment defaults.

View Astro README

What the template includes

Lean Storyblok schema

Page, article, global settings, navigation, footer, redirects, metadata, and reusable blocks stay inside a small shared contract.

Reusable page blocks

Hero, split content, grid cards, CTA, FAQ, image, article listing, and rich text blocks cover common marketing-site needs.

Generated types

TypeScript definitions are generated from the Storyblok component schema so frontend code and CMS fields stay aligned.

Preview workflow

Draft content, visual editing, and preview routes give editors a safer path to review changes before publishing.

SEO foundation

Canonical URLs, page metadata, JSON-LD support, robots controls, and sitemap generation are included as template defaults.

Deployment defaults

Each framework keeps a clear environment contract and a documented deployment path for production adaptation.

From template to launch baseline

1. Clone the template

Choose the Next.js or Astro repository, install dependencies, and run the local development server.

2. Connect Storyblok

Use the shared schema, content token, preview secret, and visual editor URL for the selected frontend.

3. Customize content and design

Update stories, globals, design tokens, media, and any project-specific copy before adding new schema.

4. Deploy

Set production environment variables, verify previews and sitemap output, then deploy through the chosen hosting target.

Built for editors and developers

Editors compose real pages

Content teams can build pages from reusable sections, manage articles, control global navigation and footer content, and preview changes before publishing.

Developers keep a small contract

Engineering teams get typed components, predictable block nesting, metadata helpers, sitemap behavior, and fewer project-specific assumptions to remove.

Lean by design

What stays out

Agency-only integrations, production analytics defaults, client content, custom backend workflows, search, forms, commerce, and heavy schema assumptions are intentionally excluded.

Why it matters

The template stays easier to fork, audit, and adapt. Add new systems only when a real project needs them, then keep both frontend implementations aligned.

View Storyblok contract

Reusable blocks ready for real pages

Hero sections

Full hero and split hero patterns for first-viewport messaging.

Split content

Two-column sections for feature explanations and proof points.

Grid cards

Compact card groups for capabilities, steps, and reusable block lists.

CTA sections

Focused conversion points for documentation or agency contact.

FAQ

Accordion content for setup, customization, and project-fit questions.

Articles

Article, author, category, and paginated article overview support.

Rich text and images

Structured rich text plus Storyblok image assets with optimized rendering.

Global shell

Storyblok-owned navigation, footer, redirects, social links, and metadata.

Template FAQ

What is this template for?

It is a reusable Storyblok website starter for teams building marketing sites with Next.js or Astro. It provides a lean schema, typed components, preview support, metadata, sitemap handling, and sensible defaults without project-specific integrations.

Can the same content run in Next.js and Astro?

Yes. The template Storyblok space is designed as a shared content source. Both frontends consume the same stories and render the same lean component contract.

Which template should we choose?

Choose Next.js when your team wants App Router, React Server Components, and familiar React hosting patterns. Choose Astro when content-heavy pages, low client JavaScript, and Cloudflare deployment are the priority.

Is this production-ready?

It is a strong launch baseline, not a finished product. You still adapt branding, content, hosting, analytics, integrations, accessibility details, and project-specific workflows before shipping.

What is intentionally not included?

The template excludes agency-only systems, production analytics defaults, client claims, bespoke backend APIs, search, forms, commerce, and heavy schema assumptions until a real project needs them.

How do we customize it?

Start with Storyblok stories, global navigation, footer content, design tokens, and media. Add new blocks only when the current lean contract cannot express the page, then regenerate types in both templates.

When should we contact Makers Den?

Talk to Makers Den when you want the starter adapted into a branded, production-ready Storyblok site with the right frontend, content model, integrations, and deployment setup.

Need this adapted for a real launch?

Makers Den can turn the starter into a branded, production-ready Storyblok site with the right frontend, content model, integrations, and deployment setup.