59 Astro landing page templates, and a safe way to change them
JustStart
JustStart is a catalogue of 59 Astro landing page templates I built and sell myself. Each one is a complete site rather than a hero section: navigation, real routes, a working contact path, a wired blog and a 404, in static output with self-hosted fonts and not one third-party request. What you actually pay for is the part that is hard to buy anywhere else, three Claude Code skills shipped inside every template, so someone who does not write code can change the thing without quietly breaking it. Four of the fifty-nine are free, because anything you could get free from a contributor on GitHub should not carry a price.
- Define the catalogue
- Fifty-nine worlds across ten industries, each loud in exactly one channel and deliberately quiet in the other three, so they do not read as one design system in different paint.
- Build the templates
- Astro 7 and Tailwind 4, static output, self-hosted fonts, a strict CSP and no third-party requests. Every brand shown is invented.
- Write the three skills
- dev-workflow, dev-test and dev-review, bundled into every template so the buyer can change it without reading the whole codebase first.
Project Details
Key information about the project scope and deliverables
Client
Wunderlandmedia
Industry
Developer Tools / Templates
Duration
2 months
Year
2026
Services Provided
Live Website
https://juststart.nowChallenge & Solution
How we transformed obstacles into opportunities
The Challenge
A landing page template that is only a hero section leaves the buyer stranded the moment they need a second route, a contact form that goes somewhere, or a blog.
Template buyers are increasingly non-developers editing with AI. They can get a change made; what they cannot do is tell whether it broke something else.
Fifty-nine templates means fifty-nine deployments, fifty-nine domains and fifty-nine sets of screenshots. Manual upkeep would not survive the first update.
The demos have to be iframed on the showcase, but the X-Frame-Options header that blocks exactly that is part of what the buyer receives and must not be edited.
Our Solution
Every template ships as a complete site, not a section: navigation, real routes, a working contact path, a wired blog and a 404.
Three skills ship inside each one. dev-workflow works out what couples to what before editing, dev-test proves the change still works, dev-review catches what the first two missed.
One data file is the single source of truth for the catalogue, and the build asserts the expected count so a bad parse fails loudly instead of half-working.
The deploy step copies dist/ and rewrites the copy, dropping X-Frame-Options and scoping frame-ancestors to the showcase. What a buyer downloads stays byte-identical to the product.
Workflow
Our Process
A systematic approach to delivering exceptional results
Define the catalogue
Fifty-nine worlds across ten industries, each loud in exactly one channel and deliberately quiet in the other three, so they do not read as one design system in different paint.
Build the templates
Astro 7 and Tailwind 4, static output, self-hosted fonts, a strict CSP and no third-party requests. Every brand shown is invented.
Write the three skills
dev-workflow, dev-test and dev-review, bundled into every template so the buyer can change it without reading the whole codebase first.
Automate demos and shots
A live demo per template on its own subdomain, and a scripted screenshot pass so the grid never drifts from what ships.
Ship checkout and go live
Polar checkout per template plus an all-access bundle, four templates released free.
Results & Impact
Measurable outcomes that demonstrate the success of our collaboration
Project Gallery
Visual showcase of the project's key features and design elements