A premium HTML pack is a folder. Netlify and Cloudflare Pages will serve it if index.html is at the publish root, forms have an endpoint, and you do not upload node_modules. Git is the adult path. This is a working note from the VicanTheme journal, written for operators and developers putting a bought pack on a static host. The catalog we keep returning to is HTML templates, because files you can host beat a locked builder when the brand has to last.
If you already know the industry, skip ahead to the recommended demo — Aether — and use the headings as a checklist rather than a speech.
What the host needs to see
Both Netlify and Cloudflare Pages want a directory whose index.html is the homepage. If the author nested the site in a src or dist folder, set the publish directory to that folder, not the repo root. Do not upload node_modules, PSD files, or a second copy of the ZIP. Aether’s fleet pages, Maris’s charter deck, and Grove’s project index are static files. They do not need a server runtime.
Connect git rather than dragging a ZIP in the dashboard forever. A vendor-original branch plus main with overrides means a recast is a push. Drag-and-drop demos are fine for an hour. They become folklore when nobody knows which laptop holds production. Set the production branch explicitly. Preview deploys on pull requests are useful if you rewrite copy. They are noise if the site changes twice a year.
Build commands, or the courage to have none
If you only edit HTML and committed CSS, the build command can be empty. If you compile SCSS, use the exact npm script the README names, with a Node version pinned. Mixing Dart Sass with a leftover binary is how colours vanish. Do not invent Vite on deploy day to feel modern. Aether does not become a better dispatch site because the pipeline is fashionable.
Environment variables belong to form endpoints and analytics, not to theme colours, if you can help it. Colours should live in tokens you compile. Secrets should never sit in the public repo. Static hosts will happily publish a forgotten dotenv file if you ask them to. Check the deploy log for the publish directory and the file count. A deploy that publishes three files is the wrong folder.
Forms, redirects, and headers
Netlify Forms can eat a native form if you add the netlify attribute; Cloudflare will not. Many VicanTheme packs expect a generic action URL. Point it at a serverless function, a form service, or a mailto you will answer. Do not leave the demo action in production. Dispatch and charter enquiries are the product. A 200 page that sends nowhere is a failed launch if the jet photograph is perfect.
Put redirects in the host’s file, not only in your head, when you replace an old site. HTML themes do not magically map WordPress permalinks. Add security headers the host supports: a sensible Referrer-Policy, not a CSP so strict it blocks your own images. Cache HTML briefly and images for a long time. Fingerprint CSS when tokens change.
DNS, HTTPS, and the last boring checks
Point the domain at the host with the records they document. Wait for HTTPS to provision before you send a client the URL. Mixed content from http demo assets will look like a broken luxury site. Search the pack for hardcoded preview URLs and replace them. Then open the live site on a phone on cellular, not office Wi-Fi. Aether’s maps and Maris’s horizon images are heavy; confirm they arrive.
Write the host, the git remote, and the form endpoint in the same note as the license id. That is the deploy. When a season recast happens, you push. You do not FTP from a contractor’s desktop. Worldwide teams especially need this because laptops and timezones multiply. Static HTML on Netlify or Cloudflare Pages is dull on purpose. Dull is how a dispatch desk and a landscape practice stay live.
Questions people actually ask
Should we use Netlify or Cloudflare Pages?
Either will serve a folder. Pick the one whose DNS, forms, and preview deploys match how often you edit. Do not split a brochure across both without a reason.
Do we need a build plugin for a vanilla pack?
No. Empty build and a publish directory are enough when CSS is already compiled. Add a Sass step only if you actually compile on the host.
Keep reading: Aviation and private dispatch website design: layout that does the job and Best HTML template for aviation and private dispatch sites in 2026. Or browse Development in the journal.
