Package a web proof without broken assets
Turn an existing static page into a clean review folder with traced image paths and a named revision.
A self-contained static proof folder, asset inventory and release receipt, ready for an authorised review.
Original FreeStack editorial workflow, checked 13 November 2026. They are not a provider screenshot, tested deployment or customer result.
About this guide & its examples
The fictional invitation and release receipt illustrate packaging decisions.
Illustrations are FreeStack concepts, not provider screenshots. Check the free limits below and test your own files before delivery.
Free boundaries before you start
What’s free, whether you need an account, and when we last checked.
VS Code · checked 2026-11-13
Microsoft product licence distinct from MIT source; free core desktop editing, extensions and AI services separate.
No provider account is required for core local work; optional stores and services may require accounts.
LibreOffice · checked 2026-11-13
MPL2.0 office suite plus component licences. Local documents have no provider credit, watermark or seat quota.
No provider account is required for core local work; optional stores and services may require accounts.
A small example to aim for
The picture travels with the page.
Clean folder → copied-folder check → sharing decision.
Receipt stays outside the public folder. Illustration only, not a provider screenshot or tested deployment.
Illustrative example · adapt it to your project.
Jump to a step
Choose a self-contained proof
Use a fictional one-page event invitation with approved text and your own artwork. The output is a folder a reviewer can open, a file inventory and a release note. Leave forms, analytics, payments, logins, remote fonts and external scripts out of this exercise. Those need separate runtime and privacy decisions.
Keep one clean release folder
In VS Code open a copy of your existing static page. Put index.html at the top and images and styles in named subfolders. Use relative paths such as assets/card.png. Do not copy a whole working directory: exclude credentials, environment files, private notes, caches and unused client assets. This is packaging, not a tutorial for building an app.
Check every asset reference
Search the HTML and CSS for src, href and url references. Compare each local path with an actual filename, including letter case. Remove machine-specific absolute paths. A file that works from your desktop may fail on a case-sensitive host. Note deliberate external links separately and verify their destination.
Test the copy you intend to send
Copy the folder to a different location and open its index.html in a browser. Check images, navigation, layout at a narrow width, readable contrast and a useful page title. Disconnect the network for a second pass to expose hidden remote dependencies. Local file checks do not prove hosted routing, headers, security or accessibility. Record pass, fail or not tested rather than guessing.
Write a short release receipt
In LibreOffice record the release label, date, intended viewer, included filenames, known limits and approval state. Keep it outside the public web folder. Compare the final copy with the inventory. If you make a correction, give the package a new revision and repeat affected checks; do not silently swap files after approval.
Choose sharing only after the proof works
Use approved delivery storage or evaluate a small hosting plan against audience, expiry, bandwidth and file limits. Spacefast is an optional catalogue product, not required for this local kit. Claim any anonymous publication before relying on its link. Use Save this toolkit for VS Code and LibreOffice. FreeStack editorial upgrade triggers: a governed review history, required runtime, justified traffic allowance or supported client handover. Buy only for a named requirement.
Your workflow, connected.
Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.
Provider information
Check current plans and documentation before committing to a workflow.
A couple of useful questions
What stays free?
VS Code core desktop editing and LibreOffice local documents have no provider export-credit, watermark, storage or seat allowance. VS Code distributions use Microsoft terms; LibreOffice uses MPL 2.0 plus component terms. AI extensions, hosting, devices and imported assets are separate.
Do I need an account?
Core local editing and document work do not require provider accounts. Optional extensions and sharing services can. A private FreeStack account stack requires sign-in; guest saves stay in that browser.
Can I publish by double-clicking index.html?
That only opens a local file. Hosting is a separate choice. Review the actual published URL, audience and asset behaviour after deployment; do not treat a local check as a production test.
Why not upload everything?
A working folder can contain secrets, unused assets and private notes. Build a clean release copy with only files required by the page, then inspect the exact copy being handed over.
What would you try?
Share your result or ask a specific question about this workflow.
Join the conversation