Release workflow
Prepare the files.
Verify the delivery.
- Replace the synthetic product copy in your config; retain explicit requirements and limitations.
- Generate a new public folder. Keep source/private delivery files outside it.
- Copy an approved free sample into samples/. Run the local checker and inspect every staged file.
- Preview all pages on desktop/mobile and follow every local link.
- Review current hosting eligibility/capacity; upload only the public folder.
- Save paid files in your delivery platform. Verify the persisted attachment, downloaded hash, license and instructions.
- Owner completes identity, payments and required agreements. Run the platform's permitted checkout/delivery test.
- Only then assert the live verification flags and add the real external checkout URL. These flags record your review; they do not perform it.
What the included checker does
Checks local quoted HTML href/src references, fragment targets, duplicate IDs, known forbidden file paths/extensions and symlinks inside a bounded public folder. External URLs are recorded but not fetched. It does not detect all secrets, validate paid checkout, scan malware or provide access control.
Current platform references
Netlify pricing · Payhip pricing · Payhip content-editor delivery rules. Check these again before release; free tiers and terms can change.
Record evidence
Use RELEASE-REGISTER.md in the source kit. Keep exact package hashes, checks, public URLs, owner actions and remaining uncertainties. A passing local check is not proof of demand or sales.