How to edit and publish an HTML template

Choose your starting point

FlowState is a fintech and SaaS landing page with contact and legal pages. AxisBlue is an analytics and B2B SaaS landing page with a three-step contact demo. Beaute is a beauty and skincare salon landing page with a reservation demo. Crafters Inc. is a construction and renovation company website with a static blog and an inquiry demo. PaywaveJP is a multi-page fintech website with two home layouts, pricing, integrations, company information, articles, and demo forms. All five include English pages in en/, with their own assets.

Explore the FlowState English preview, AxisBlue English preview, Beaute English preview, Crafters Inc. English preview, or PaywaveJP English preview before editing. The previews show sample products. Payments, accounts, integrations, and form delivery are not connected.

1. Open the project

Unzip the download and keep the template folder together with its assets. Preview it with a local web server. Opening HTML directly from a file can behave differently from a hosted site.

For example, if Python 3 is installed, open a terminal in your extracted template folder and run python3 -m http.server 8000. Visit http://localhost:8000/en/. Keep the local server open while you review the pages; it does not publish your files online.

MDN: using a local testing server ↗

2. Find the pages

FlowState, AxisBlue, Beaute, Crafters Inc., and PaywaveJP include English pages: open en/index.html and keep its assets together. The original Japanese pages remain at the top level. FlowState includes contact/, legal/privacy-policy/, legal/term-of-service/, and 404/. AxisBlue includes contact/, privacy/, terms/, and 404/. Beaute includes reservation/ and supporting privacy, terms, cookie, legal, security, and 404 pages. Crafters Inc. includes about/, blog/ and three article folders, contact/, privacy/, terms/, and 404/. PaywaveJP includes index.html, home-2/, features/, pricing/, integrations/ and six detail pages, about-us/, careers/, blog/ and six articles, faq/, contact/, privacy/, terms/, and 404/. Asset folders contain images, fonts, styles, and scripts. Design reference pages are internal tools.

3. Make it yours

Replace the brand, logo, copy, images, product screens, pricing examples, contact details, and footer. Search the entire folder for old addresses, sample statistics, and quotes. Update page titles, descriptions, language attributes, social images, image alternatives, and links.

Edit one section at a time and reload the preview. Preserve image paths and filename capitalization. Replace sample testimonials and metrics with information you can substantiate; remove a section when you do not have suitable evidence. Set canonical and social-image URLs to your own final domain, then update structured data so it describes your real business.

4. Connect the form

The included forms are demos. Add a form service or your own backend, then verify delivery, validation, consent, server failures, and spam handling. Keep the demo label until a real connection works.

5. Review every page

Check mobile and desktop layouts, menus, pricing controls, keyboard access, reduced motion, external links, legal placeholders, and the 404 page. Check animated and duplicated text after editing.

6. Publish and verify

Follow your host’s static-site workflow. Configure directory URLs and 404 responses. Open the live pages, check assets and fonts, and test real form delivery. A local preview passing does not prove the live site works.

For an English-only site, the contents of en/ are the starting publish folder: its index.html, asset folder, scripts, and supporting page folders must stay together. Keep an untouched copy of the complete download separately. Do not publish only the homepage HTML or move assets without updating references.

On Cloudflare Pages, Direct Upload accepts a folder or ZIP through the dashboard. Upload the site you customized, then open the provided preview URL before connecting your domain. With Git integration and no build step, Cloudflare documents exit 0 as the build command; the output directory must be the folder containing your site’s index.html. Never put secret keys in downloadable or publicly hosted files.

The supplied 404/ design is a page, not a hosting rule. Cloudflare Pages looks for 404.html; without a top-level 404 file it can fall back to the homepage for unknown routes. Configure your host’s error page and verify that a made-up URL returns HTTP 404. Check nested-page assets after copying the 404 design to another location.

Cloudflare: Direct Upload ↗ · Static HTML setup ↗ · Routes and 404 behavior ↗

Choose hosting that keeps your template source private. LANSO’s one-project license permits a published website but does not permit redistributing the template source as a reusable product. A public source repository can expose the complete download.

7. Keep your release

Keep your original download, edited source, and purchase details. Check your LANSO purchase history for the currently published version and compare changes before replacing a customized site.

If the published page looks wrong

• Missing images or fonts: check the browser’s Network panel for 404 responses. Confirm that the asset folders were uploaded and that paths match filename capitalization.
• The homepage works but contact pages break: open the nested URL directly, then review links and asset paths relative to that page. Test the actual domain or subdirectory you will use.
• A form advances but no message arrives: the supplied interaction is a demo. Connect delivery and test the inbox or destination, validation, failure state, and confirmation with a real submission.
• An unknown URL shows the homepage: inspect the response status and configure your host’s 404 handling instead of relying on the visible error-page design alone.

Before sharing your live URL

• Open the homepage, contact page, every legal page, and an unknown URL on the final domain.
• Check phone and desktop layouts, keyboard navigation, menu links, and reduced-motion behavior.
• Verify that images and fonts load, social previews use your assets, and titles, descriptions, language, canonical URLs, and structured data describe your site.
• Submit the connected form and confirm the received message. Test invalid input and a sending failure as well as success.
• Replace sample claims and legal placeholders, keep a backup, and retain your purchase details.

Maintained by LANSO. Hosting instructions checked against the linked documentation on 2026-10-23. Hosting interfaces can change; follow your provider’s current instructions. A published page does not by itself confirm search indexing.