Getting started
Install a Build2Next theme, run it locally and put it online. These steps use the commands every theme ships with; the theme's README has the details for its own files.
Requirements
- Node.js 22.23.4 or newer (the minimum for Astro 7; themes pin it in
.nvmrc). - npm 9.6.5 or newer. pnpm and Yarn work too.
- A code editor and a terminal.
Install and run
Unzip the theme, open a terminal in its folder and run:
npm ci # install the exact dependencies from package-lock.json
npm run dev # local development at http://localhost:4321
npm run build # static site in ./dist
npm run preview # serve the production build locallyIf the theme has no package-lock.json, use npm install instead of npm ci. The theme also ships npm run check (type-check), npm run lint and npm test; run npm run check after you make changes.
Where to change content
Each theme keeps its copy in src/data/ — navigation, footer, pricing, page text and the sample content inside the product mockups. Blog posts and other collection entries live in src/content/ as Markdown. Add a file, and its page, list entry and feed item are generated for you.
Colours, fonts and styles
Each theme keeps its colours, font sizes, radii and shadows in one tokens file: src/styles/tokens.css in Saasar. The theme's README lists the exact files for that theme, including its base and layout styles.
Deploy
Any static host works: Cloudflare Pages, Netlify or Vercel, for example. Point the host at the repository or upload the built folder, then set:
- Build command:
npm run build - Output directory:
dist
Before you deploy, set site in astro.config.mjs to your domain, and copy .env.example to .env to fill in any form endpoints the theme uses. The theme's README lists the variables.
Update a theme
- Download the new version from Lemon Squeezy My Orders.
- Read
CHANGELOG.mdand anyUPGRADINGnotes included with the release. - Copy the changed files over your project, keeping your own content and customisations. The upgrade notes say which files changed.
Updates are free for life, so you can stay on the latest version at no extra cost.
Get help
If something does not work, read the theme's README first, then see Support for what to include when you email us. Every purchase includes 12 months of support for installation and bugs.