Original static source kit · 0.1.0

Your preview and paid files need different homes.

Generate a small catalogue, describe exactly what a buyer receives, and check local links and known prohibited files before hosting the public folder.

Inspect the two-product example →Download one-product free sample

Editable pages

One JSON config creates a catalogue, product details and quick-start pages, with metadata and a sitemap. No framework, runtime API, hosted database or external fonts.

The filled utility and recipe examples are synthetic page content, not two additional implemented software products.

A repeatable preflight check

The full kit checks quoted local HTML references, missing fragments, duplicate IDs, symlinks and known prohibited files such as full ZIPs, private folders and environment files.

External links are listed without being fetched. Scripts and forms need manual review.

Free sample or full kit?

Free: generator, editable one-product example, stylesheet, one synthetic CSV and generated static preview.
Full: all three page views, two distinct filled examples, local checker and policy, regression checks, release register and delivery checklist.
Both: explicit requirements and limitations, prepared checkout state, first-name attribution and original source.

Many free landing themes already exist. Choose this experiment only if its file staging and review workflow helps you. A template cannot establish demand or guarantee revenue.

From files to a reviewed preview

Replace the synthetic example copy with your own real product and prerequisites.
Use Node.js 22+ to generate a new public folder. Copy only approved free samples.
Run the included full-kit checker; inspect every staged file and follow the pages on desktop/mobile.
Host the public folder. Save full paid files on a separate delivery platform.
Owner verifies payments, agreements and actual customer delivery before enabling an external checkout link.

Follow the worked walkthrough

Know the boundaries

Will it host or sell my product automatically?

No. It produces static files and local review output. You control the host, delivery account, identity and payment authorization. No automated account creation or fees are included.

Does a passing check prove that paid files are private?

No. Every staged public file is readable. The checker recognizes selected paths/extensions and authored HTML references; it does not detect all secrets, inspect ZIP contents, parse arbitrary scripts/CSS URLs or provide access control. Review the complete public inventory manually.

Can I use generated pages for my own commercial products?

Yes, under the included license. Publishing generated pages is permitted; reselling the full paid source kit as a competing template collection is excluded.

What costs remain?

This site and tooling require no paid runtime. Hosting and delivery providers have changing limits, transaction fees and eligibility rules. Check their current terms before choosing a plan or activating sales.