Choosing a stack

Many templates come in more than one version. The design, pages and features are the same in every version; only the code differs. Pick the one that matches how you like to work.

HTML + Tailwind CSS#

Plain .html files with pre-compiled Tailwind CSS v4 and a small vanilla JavaScript file.

• No tools needed. Open index.html and edit with any text editor.
• Hosts anywhere: drag the folder onto Netlify, push it to GitHub Pages or upload it over FTP.
• Best for small business sites, portfolios and anyone who wants to edit files directly.
• Trade-off: the header and footer are repeated in every page, so site-wide changes mean editing each file (a project-wide find and replace works well).

Every template has an HTML version.

Next.js#

A Next.js 16 App Router project in TypeScript with React 19 and Tailwind CSS v4.

• Components: the header, footer and sections are written once and reused.
• Data files: repeated content (plans, products, rooms, team) lives in src/data/, so adding an item is a one-line change.
• Static by default: output: "export" in next.config.ts makes pnpm build write plain HTML, CSS and JavaScript to out/, so it still deploys to any static host.
• Room to grow: remove static export and you can add API routes, Server Actions, a database or authentication, then deploy to a host that runs Node.js, such as Vercel.
• Best for developers who already work with React, and sites that will grow beyond a brochure.

Every template has a Next.js version.

Astro#

An Astro 7 project in TypeScript with Tailwind CSS v4, built as a static site.

• Components without the weight: pages and sections are .astro components written once and reused, and they render to plain HTML at build time. Interactive features run as small client-side scripts, so pages ship very little JavaScript.
• Data files: repeated content lives in src/data/, like the Next.js versions.
• Static output: pnpm build writes plain HTML, CSS and JavaScript to dist/, ready for any static host (Netlify, Vercel, Cloudflare Pages, GitHub Pages).
• Room to grow: add Markdown or MDX content collections for a blog, or an adapter for server rendering when you need it.
• Best for content-led sites where speed matters, and developers who like components but don't need React.

Every template has an Astro version.

WordPress#

A WordPress block theme for WordPress 7.1 or later, edited entirely in the WordPress Site Editor.

• No code needed: every heading, paragraph, image and button is a block you can change in the editor. Colours, fonts and spacing are theme presets, so Appearance > Editor > Styles restyles the whole site.
• Pages from patterns: each page is built from the theme's patterns. After you activate the theme, its setup screen creates the pages and the menu in one click, and the patterns stay available to add to new pages.
• Same design and features: the theme uses the template's stylesheet and scripts, so it looks and behaves like the HTML version, including dark mode.
• Try before you install: Try in WordPress Playground on the template page opens the theme in a complete WordPress site that runs in your browser, with nothing to install.
• Best for sites that non-developers will update, and anyone already hosting WordPress.

Every template has a WordPress version. Each template's documentation lists the stacks it has.

Templates with more than one version show a Stack switch on their page. The live preview, version number, documentation and download all follow the stack you pick.

Follow the changelog for new templates, or vote for what we build next on template requests.

Comparison#