Publish a static preview while keeping paid ZIPs out of public files
A preview should show what a download does without accidentally shipping the full paid archive in public assets. Inspect the release boundary, requirements and delivery path before adapting the example site.
For: Developers preparing a preview for a downloadable product.
A useful starting sequence
- Open the free fixture-notes example and inspect its public preview files.
- Follow the release-boundary walkthrough and check what happens when a synthetic paid file is placed in public assets.
- Adapt the generator and delivery register only after checking your own platform and license. Connect your own real checkout separately.
One concrete example
A full archive is copied next to a landing page during deployment. Hiding its link does not make the archive private. The release checker examines the declared public file boundary; the example checkout stays deliberately closed.
Choose the part you need
Use it when: Developer selling a local/downloadable utility with a free public preview.
Free: The fixture-notes preview and release walkthrough are free; the illustrative checkout is closed.
Paid adds: Static generator, file-boundary checker and release documentation.
Limit: Example checkout is intentionally closed. The kit does not supply buyers, payments or private hosting.
Inspect the proof and download details →Start with a free alternative when it fits
A static generator such as Eleventy and a hand-written release script may be enough. This kit provides an original bounded generator, boundary checks and release documentation; it does not supply customers or private hosting.
Eleventy static generator. These independent downloads are not endorsed by the linked providers.
Do I need to buy every tool in this group?
No. Run the relevant free example first. Buy one prepared workflow only if its contents and requirements match your current task. The group is a navigation guide, not an additional bundle or subscription.
What does a successful example prove?
It shows the named synthetic behavior in the documented environment. It does not certify a production application, establish compatibility with every editor or substitute for your own integration tests.
Inspect the release evidence and limitations · Choose another workflow