cPanel / InMotion / HostGator
File Manager
- Open File Manager.
- Enter
public_htmlor your domain root. - Upload the ZIP and extract it.
- Move the extracted contents up one level if needed.
- Confirm
index.htmlis directly in the root.
Keep the line moving
The complete self-service guide for getting a Web Chef template online, customizing it safely, and fixing the usual hosting problems.
01 · Quick start
Do these steps in order. Most failed installs come from uploading the outer folder instead of its contents.
Extract the ZIP on your computer. Inside it you should see index.html, admin, assets, and data.
In your host, open the folder that serves your domain. It is commonly named public_html, www, htdocs, or the domain name.
Upload everything inside the extracted folder. The file index.html must sit directly in the document root—not one folder deeper.
Open your domain in a private browser window. Refresh once with the cache bypassed if you previously had another site there.
Visit yourdomain.com/admin/. Use the demo password shown in your INSTALL.txt, then set your recovery phrase and export a backup.
The $297 template is a static site. Admin edits are stored only in the browser where you make them; they do not sync to other devices or publish server-wide. Use the admin to explore and prepare content, and export JSON before clearing browser data. Choose Web Chef hosting if you need shared, persistent live updates managed for you.
02 · Pick your host
The site must be served from the domain root with HTTPS enabled.
cPanel / InMotion / HostGator
public_html or your domain root.index.html is directly in the root.Netlify
Cloudflare Pages
Other static hosts
index.html.The instant-template build expects to run at a domain root such as https://yourtruck.com/. Installing at https://example.com/my-truck/ can break asset paths.
03 · Owner admin
/admin/ on your primary phone or computer.INSTALL.txt.Private browsing, browser cleanup tools, or clearing site data can remove these. Export before switching devices.
04 · Customize safely
05 · Backups and moves
In admin, open Settings → Data → Export JSON. Keep the dated file somewhere outside your browser.
On the same template, open Settings → Data and choose the exported file. Review the site after import.
Export on the old device before opening admin on the new one. Passwords and recovery phrases do not travel with the content export.
06 · Troubleshooting
Open the row that describes what you see.
index.html is not in the document root, or the host still prefers an older index file. Move the template contents into the root and rename or remove the old placeholder index after making a backup.
The site is probably installed in a subfolder. Move it to the domain root. Also confirm the assets folder uploaded completely and that file names kept their capitalization.
Open the domain in a private window, then clear the host/CDN cache. If WordPress was previously installed, confirm the server is loading index.html instead of index.php.
Passwords are stored in each browser. The new device starts with the demo password from INSTALL.txt. Set a new password and recovery phrase on the device you plan to use.
The instant template stores edits locally in one browser; it is not a server-synced CMS. Export your JSON for backup. If you need shared persistent updates, use the hosted package.
Browser data was likely cleared, private browsing was used, or the domain changed. Import your last JSON backup. Without an export, browser-local changes may not be recoverable.
Convert it to JPG or WebP, reduce it below 3 MB, and try again. Very large images can exceed browser storage. Export a backup before removing other images.
Enable the host's SSL certificate and force HTTPS in the hosting panel. Certificate provisioning can take several minutes after connecting a domain.
Your DNS is not pointed at the host yet, or propagation is incomplete. Follow the host's exact DNS records and allow up to 48 hours, though most changes appear sooner.
Not as a theme or plugin. This is a standalone static website. It replaces the public site at the domain root and does not require those platforms.
07 · Still stuck
Support is for problems with the delivered Web Chef files—not general hosting administration, DNS management, third-party platforms, or custom code changes.
Never email passwords, recovery phrases, hosting credentials, or payment information.