jt. THE WEBSITE FIELD GUIDE
Publishing
JOHNNY TANG TEMPLATES / YOUR STEP-BY-STEP GUIDE

Your website.
Your words.
Your own little address.

A practical walkthrough from opening your template to publishing it on a domain you own. Use a computer for editing and uploading. You do not need a terminal, a code editor, or a design-platform subscription.

The editor and template files are included in the customer package. This is the complete written walkthrough.

The template

The actual website files: the design, words, images, and interactions.

Hosting

The service that puts those files on the internet.

Your domain

The address people type, such as yourname.com. Usually renewed yearly.

01

Open your template.

  1. Download the customer package to your computer and unzip it. On macOS, double-click the ZIP. On Windows, right-click it and choose Extract All.
  2. Open START-HERE.html in your browser to read this guide. Open EDIT-ME.html to personalize your website.
  3. If a text editor opens, right-click the HTML file and choose Open With → your browser.
Johnny Tang Templates / START-HERE.html ← this guide EDIT-ME.html ← your local editor website/index.html ← original sample website LICENSE.txt FONT-LICENSES.txt

Success looks like this: the editor shows editable fields and a working preview. No account is needed to edit your template.

02

Change the words. Choose your photos.

  1. In Website basics, set the browser title, short description, and your public contact email. Leave the website address blank until you have a domain.
  2. Open each content section. Replace the sample name, headline, introduction, services, project stories, location, and footer. The preview follows the section you edit.
  3. Open Photos & project covers. Choose your JPG, PNG, or WebP images, up to 12 MB each. The editor makes web-sized copies locally.
  4. Describe each image for visitors using screen readers. The example covers and sample person are demonstration content; replace them with your own work and details.
  5. Use Desktop / Phone to compare layouts. After editing, test the exported page too.
EDITOR → YOUR WEBSITE / STRUCTURE EXAMPLE
Your name: Jamie Chen
Jamie Chen.
A diagram of the editing process, not a screenshot of a hosting service.

Email buttons open the visitor's configured email application. These templates do not collect form submissions, accept bookings, or process payments. The editor language button translates the controls; it does not automatically translate your website copy.

03

Keep an editable copy. Export the website.

  1. Click Save editing file. Keep the downloaded JSON beside the template folder. This file preserves your text and replacement images.
  2. Click Export my website .zip. You will get a separate ZIP, such as folio-website.zip.
  3. Unzip it into a new folder. Open the index.html at the top level to check the result. Images, fonts, and interactions are included in that HTML.
  4. Keep the downloaded ZIP ready for Cloudflare, or the extracted folder ready for Netlify.

You now have two different things: an editing JSON for future changes, and a website ZIP for publishing. Upload only the website ZIP or its extracted contents.

Saving an editing file or exporting a ZIP does not update any live website. Closing the editor without saving can lose unsaved changes.

04

Give your website an address.

You can test on a hosting service's default address before buying a domain. When ready, use an account you own.

  1. Open Cloudflare Register domains ↗, sign in, and verify your account email.
  2. Search for the exact name. Compare the registration price and renewal price, then select an available domain.
  3. Enter accurate registrant and payment details. Review the term, auto-renew settings, and agreements before completing your own purchase.
  4. Complete the registrant verification email and confirm that the domain is active.

Official domain registration guide ↗

Domains bought through Cloudflare Registrar keep Cloudflare nameservers. You can still use another host by setting the appropriate DNS records. A domain purchase does not automatically give you an email inbox.

Domain registration, renewals, and any hosting charges are paid separately to the chosen provider. Check its current plan and usage terms; this template does not require a paid visual editor.

05

Upload it. Connect your domain.

Pick one of the two complete paths below. The main Cloudflare walkthrough uses Pages Direct Upload because its manual upload and update flow is documented together.

A / Publish on Cloudflare Pages

  1. Open Workers & Pages in your Cloudflare dashboard. Choose Create application and the Pages / Get started / Drag and drop path.
  2. Name the project. Upload the website ZIP you exported, with index.html at its root. Select Deploy site or Save and Deploy.
  3. Open the resulting project-name.pages.dev address and check the site.
  4. In this Pages project, open Custom domains → Set up a custom domain. Add your domain and follow the DNS instructions. For an apex domain on Pages, its zone must be active in the same Cloudflare account.
  5. Add www.yourname.com separately if you want that address too. Wait for DNS and HTTPS activation, then test both addresses.

Upload & update docs ↗ · Pages custom domains ↗

Pages and Workers use different domain screens. Follow the screen for the product you created. Do not delete unrelated DNS records, especially existing email records.

Optional: try Cloudflare Drop first

Cloudflare Drop ↗ accepts your website folder or ZIP. The initial preview lasts 60 minutes; choose Claim and sign into your account to keep it. After claiming, you can connect or buy a domain. This creates a Worker; its domain settings differ from Pages. The main tutorial above avoids mixing these two flows.

Official Drop walkthrough ↗ · Worker domain settings ↗

06

Keep your website up to date.

  1. Open the original EDIT-ME.html and choose Open editing file. Select the JSON you saved last time.
  2. Make changes. Save a new editing file and export a fresh website ZIP. Keep the previous ZIP as your backup.
  3. Cloudflare Pages: open the existing project, choose Create a new deployment, select Production, and upload the complete updated website ZIP.
  4. Netlify: open the existing project's Deploys page and use its manual upload area for the complete extracted website folder.
  5. Visit the same custom domain. Check the changed content and links. Use a private browser window if an older version is cached.

Update the existing project. You do not need to purchase the domain again or create a new project for each text change.

Pages updates ↗ · Netlify manual deploys ↗

07

A short check before you share.

Use these checks on the exported website and on the final domain. Tick them as you go.

0 / 6

?

A little help, if you get stuck.

I see a 404 page.

Check that index.html is at the root of the uploaded ZIP or folder, not inside an extra parent folder. Confirm the deploy completed. If the default hosting URL works, check the custom-domain configuration next.

My changes disappeared.

Open EDIT-ME.html, then import your saved editing JSON. A website ZIP is a publishing copy, not an editing file. If you never saved before closing, those unsaved changes may not be recoverable.

A photo will not upload.

Convert HEIC or unsupported images to JPG, PNG, or WebP first. Choose a file smaller than 12 MB. Portrait and landscape frames crop differently; use a photo with room around the subject.

My email button does nothing.

Email links are disabled inside the editor preview. Test the exported index.html. Visitors need a configured email app; the visible address can also be copied into webmail.

The domain works without www, but not with it.

These are two hostnames. Add the missing hostname to your hosting project and follow its DNS instructions. Do not remove existing mail records. Wait until both domain and certificate statuses are ready.

Can I edit layout or add payments?

This editor changes existing content and images. The supplied HTML can be developed further, but new layouts, databases, payments, or forms require additional implementation. Keep a copy of the original package.

This is a written guide with editing illustrations. Hosting instructions were checked against official documentation; exact dashboard layouts may change. Customer account creation, purchases, DNS changes, and deployment are completed in the customer’s own account.