Runnable React + Vite project
`src/Template.tsx`, `src/main.tsx`, project configuration and pinned top-level dependencies.
BUYER GUIDE · DEVELOPER HANDOFF · POLICIES
Know exactly what you get—and what comes next.
A truthful guide to the source files, demo functionality, setup, customisation and launch responsibilities in every template package.
01 / THE DOWNLOAD
Inside every template package.
The purchased design system
Responsive layout, motion and the complete set of demo views shown in the live preview.
Media supplied for redistribution
Approved local concept artwork is bundled in `public/media`; every reference is recorded in `ASSET-MANIFEST.json`.
Buyer and developer documentation
`README.md`, `SETUP.md`, `DEVELOPER-GUIDE.md`, `CONTENT-CHECKLIST.md`, `LAUNCH-CHECKLIST.md` and `SUPPORT.md`.
Single-site licence
A named licence for one business website, plus the right to customise and publish that site.
02 / BOUNDARIES
What is not included.
- Hosting, a domain name, deployment or ongoing website management.
- Live forms, bookings, payments, customer accounts, search services, databases or a CMS.
- Business copy, legal advice, product data, photography or third-party media licences.
- Guaranteed rankings, sales, accessibility compliance or compatibility with untested plugins and platforms.
- Custom development or support beyond the separately purchased Template Care or build agreement.
03 / TUTORIAL
From ZIP file to tested build.
- 01
Install the tools
Use Node.js 22.13 or newer (Node 24 recommended) and npm. No global Vite install is needed.
- 02
Open the project
Extract the ZIP, open a terminal in the extracted folder and run `npm install`. Keep the generated `package-lock.json`.
- 03
Run it locally
Run `npm run dev`, then open the local URL printed by Vite. Navigation uses hash routes so each demo view works on a static host.
- 04
Replace the content
Edit `src/Template.tsx`, `index.html` and approved files in `public/media`. Replace fictional names, claims, prices and contact details.
- 05
Connect real services
Implement forms, bookings, payments and data on a secure server or trusted provider. Never put secret keys in frontend source.
- 06
Test the production build
Run `npm run build`, then `npm run preview`. Complete both checklists before removing `noindex`.
- 07
Publish deliberately
Deploy `dist` to a static host, configure the domain and HTTPS, then verify every route, action, policy and analytics choice.
04 / DEVELOPER HANDOFF
How to work with the files.
Project map
- src/Template.tsx
- The purchased interface, responsive styles and navigation.
- src/main.tsx
- The React entry point. Keep the supplied template import unless you deliberately restructure the project.
- public/media
- Bundled distributable concept assets. Replace files deliberately and update alt text.
- ASSET-MANIFEST.json
- The record of packaged media, external references, rights notes and demo-only functionality.
- index.html
- Business title, search description and draft noindex control.
Implementation rules
- Keep hash routing for static hosting, or configure your host to rewrite application routes to index.html.
- Keep secrets and privileged actions server-side. Validate inputs and test success, error and retry states.
- Preserve keyboard focus, labels, semantic headings, contrast and reduced-motion behaviour.
- Do not remove demo disclosures until every visible action is connected and verified.
- Run the production build and inspect every view at narrow and wide widths before launch.
05 / POLICIES
Rules that protect the buyer and the visitor.
One site
Use the source for one business website owned by you or one client. Do not redistribute, resell or turn it into a competing template library.
Truth before launch
Replace fictional content and verify claims, prices, policies, contact details and media rights before representing a real business.
Accessible by default, verified in context
The supplied project includes keyboard focus, reduced-motion behaviour and responsive foundations. Final compliance depends on your content, integrations and changes.
Secure integrations
Secrets and privileged actions belong on a server. Real forms, accounts, bookings and payments require validation, abuse protection and tested failure states.
No silent scope
Template-only, Built for you and Managed website are distinct products. A service quote must state pages, integrations, revisions, timing and third-party costs.
06 / FREQUENTLY ASKED QUESTIONS
The practical details.
Is the download a finished website?
It is a runnable frontend and design system. It must be customised, connected to any required services, tested and published.
Do the demo forms and carts work?
They demonstrate client-side journeys and review states. They do not send messages, take payments or create bookings.
Can my developer use another framework?
Yes. The licence permits modification for the licensed site. Porting is development work and should preserve accessibility, routes and content disclosures.
Are all images and fonts included?
Redistributable local concept assets are included. External references are listed in the asset manifest and must be licensed or replaced before launch.
Can I use the template for a client?
Yes, for one client business website. A separate licence is required for every additional business website.
Will the pages work on a static host?
Yes. Included navigation uses hash routes. Any server-backed feature you add may require a different hosting plan or routing configuration.
What does Template Care cover?
Compatibility fixes, template updates and email support. It does not include hosting, content edits or operating business systems.