What Is a Web Page Template? Two Products Share the Word
A hosted design you edit in a builder, and a source repo you own, are both called templates. What is actually inside one, from a catalog of 111.
A web page template is a pre-built page — layout, styles, components and placeholder content — that you fill with your own material instead of designing and coding it from nothing. The word covers two very different products, though: a hosted design you edit inside a website builder, and a source-code project you download and own. Which one you bought decides almost everything that happens next.
The two things called "template"
Search results for this term mix them freely, which is why the definitions read as vague. They are not the same product:
| Builder template (Wix, Squarespace, WordPress theme) | Code template (what this catalog sells) | |
|---|---|---|
| What you receive | An account with a design applied | A zip of source files |
| Where it runs | The vendor's hosting, only | Anywhere you can deploy — Vercel, Netlify, a VPS |
| How you edit it | A visual editor, inside their app | An editor, in code |
| What you can change | What the editor exposes | Everything |
| If you stop paying | The site goes away | The code is still on your disk |
| Who can work on it | Anyone | Someone who writes code |
| Updates | Applied by the vendor | You merge a new version, or don't |
Neither is better. A builder template is the right answer for someone who will never open a terminal. A code template is the right answer when you need the thing to be genuinely yours — and it is the only one of the two that can be handed to a developer and extended without asking permission.
Everything below describes the second kind, because that is the one we can describe from the inside.
What is actually inside one
In this catalog a template is a catalog entry plus a git repository. The entry is a typed object in src/data/catalog.ts, and it is the single source of truth for the product page, the cards, the SEO surfaces and the download. Here is a real one, abridged:
{
slug: "asoc-keystone-landing",
name: "ASoc Keystone",
seoLabel: "Mortgage Lender Website Template",
category: "landing",
status: "available",
pricing: "premium",
tagline:
"A mortgage-lender marketing site — loan products, an eligibility checker, and a quote funnel.",
features: [
"Free-quote & eligibility-check lead funnel",
"Loan products: purchase, refinance, HELOC",
"Apply / approve / close 3-step flow",
"Borrower use-case pages",
"Client stories & FAQ",
],
editions: [{ framework: "nextjs", status: "ready", previewUrl: "…" }],
latestVersion: "1.0.0",
changelog: [
{ version: "1.0.0", date: "2026-07-16", notes: ["Initial marketplace release."] },
],
}
Three fields in there are worth pulling out, because they are what separates a template product from a folder of HTML.
editions. A template is not one build. Each edition is a framework — react, nextjs, vue, angular or html — with its own repository and its own live preview. Across 111 products this catalog carries 139 editions: 110 Next.js, 10 plain React, 9 Vue, 9 Angular and 1 pure HTML.
latestVersion and changelog. A template is versioned software, not a one-time file. Buyers download the current version; when it changes, the same purchase resolves to the new one.
status. available or coming-soon. A template that never sold can be removed; one that has sold cannot, because the slug is a permanent entitlement ID. Retiring a product means marking it unavailable and leaving its download in place so existing buyers keep access.
What "you receive the files" actually means
This is the part builder templates have no equivalent of. A purchase here resolves to an object in a private bucket at a deterministic path:
{slug}/{framework}/{slug}-{framework}-v{version}.zip
The download route resolves the catalog's latestVersion, checks the buyer's entitlement fresh on every request, and hands back a signed URL that expires in sixty seconds:
/** Signed URLs are meant to be used immediately, not stored/shared. */
export const SIGNED_URL_TTL_SECONDS = 60;
Entitlements are version-agnostic on purpose. Nothing is re-issued when a template is updated — the next download a buyer starts simply resolves to the newer zip. That is the concrete difference behind the "updates" row in the table above: a builder vendor pushes changes into your live site, whereas here a new version sits in a zip until you decide to merge it.
What a template does not include
Honest scoping, because this is where most disappointment comes from:
- Your content. The template ships placeholder copy and demo imagery. The copy is the part that takes the longest and the part no template can do.
- Licensed photography. Demo images are for the demo. Anything you ship publicly needs assets you have rights to.
- A backend, usually. A landing page template is pages. Forms, auth and payments are separate work unless the product says otherwise.
- Hosting and a domain. Both are yours to arrange, which is the flip side of being able to deploy anywhere.
Why "template" and "theme" are not synonyms
A theme re-skins a system that already exists — a WordPress theme has no meaning without WordPress. A template in the sense used here is the application: it does not plug into a host platform, it is the thing you deploy. That is why the editions above are per-framework. There is no host to theme, so the framework choice is a real fork in the product rather than a setting.
A template in a third sense — the one Microsoft Power Pages and most CMSs use — is a layout file inside an app: the reusable page skeleton a route renders content into. That sense is alive in this codebase too, in src/components/templates, where each file orders the sections of a page type and holds no content of its own. Same word, three meanings, and search results for it rarely say which one they are using.
Common mistakes
| Mistake | What happens | Fix |
|---|---|---|
| Buying a builder template expecting to export the code | There is nothing to export; the design only exists inside the vendor's editor | Decide hosted-vs-owned before you buy, not after |
| Judging a template by its demo screenshots | The demo is the best possible content in the best possible layout | Open the live preview and click into the inner pages |
| Editing template files directly, everywhere | The next version becomes an unmergeable conflict | Keep customisation in your own files and config; touch template internals sparingly |
| Assuming the demo images are yours to ship | Demo photography is licensed for the demo, not for your production site | Source your own imagery before launch |
| Treating a template as a finished website | Placeholder copy ships to production | Budget the content work; it is the larger half |
| Picking a category before a framework | A great template on a stack your team can't maintain is a liability | Filter by framework first — it is the constraint you can't refactor away |
Frequently asked questions
What is a web page template, in one sentence? A pre-built page — layout, styling, components and placeholder content — that you customise with your own material rather than designing and coding it from scratch.
What is the difference between a website template and a web page template? Scope, and in practice the terms are used interchangeably. A web page template is one page; a website template is a set of pages sharing one design system. Most products sold as "web page templates" are the latter — every product in this catalog is a multi-page project.
Are web page templates free? Many are — open-source starters on GitHub are real templates and cost nothing. What you generally trade for the price is scope and support: fewer screens, no versioned releases, and no one obliged to fix anything. Every one of the 111 products in this catalog is currently premium, and what you are buying is the breadth and the maintenance rather than permission, since a permissively licensed free starter already grants you most of the rights a paid licence does.
Do I need to know how to code to use one? For a builder template, no. For a code template, yes — you need to install dependencies, run a dev server and edit source files. That is the trade for owning the result and being able to host it anywhere.
Can I use one template for more than one site? Under most commercial template licenses, including this one, the limits are developer seats and whether end users pay to access what you build — not the number of domains you deploy to.
Templates in this post
ASoc Keystone is the mortgage-lender template quoted above, ASoc Ledger and ASoc Lens are two more of the 66 landing products in this catalog — each one a catalog entry, a repository and a versioned zip, exactly as described.
Browse the full sets: Next.js landing page templates, Tailwind landing page templates. For the decisions that follow from here, see How to Evaluate a Website Template Before You Buy, How to Customize a Website Template Without Blocking Its Updates and Template vs. Building From Scratch; for what the licence actually permits, see Template Licenses Explained.