This chapter applies only when the site has the Static sites module on, and your account has the matching permission. If Static sites is missing from the sidebar, the module is off or you do not have access. Contact the platform. A site owner cannot turn this module on.
Publish a static site you already built (HTML, CSS, images, and the rest, packed as a ZIP) at its own address. It stays separate from the CMS site you build under Pages.
Under one admin account you can create up to 3 static sites. A static site is not a page inside the page editor, and it does not appear in the CMS header or footer.
Where to open it
Sidebar Static sites (/admin/static-sites). The page explains it: upload a ZIP to create a preview, then publish to a dedicated subdomain.
| Screen | What it is for |
|---|---|
| List | Name, host, and status (Live / Preview pending / Not published / Maintenance). Usage at the top right looks like 1/3 used |
| One static site | Click Manage. Upload a ZIP, confirm the preview, publish or roll back, set a password, and attach a custom domain |
After you create one, the platform subdomain looks like:
https://your-code.sites.timtech.tw
(Use the address shown at the top of the admin page.) This address is not the same layer as the CMS host your-site.timtech.tw. They do not overwrite each other. If you land on the main site’s homepage or the admin, the address is missing the .sites. piece.
Who can do this?
By default the owner and a site editor can create, upload, and change settings. A viewer can usually only look.
A sensible order
- On the list, fill Name and Subdomain slug, then click Create.
- Open that site and Upload ZIP (50MB per file). See Create a site and upload a ZIP.
- When the deploy finishes, confirm with Open preview, then Publish. See Preview, publish, and roll back.
- To use your own domain, see Attach a domain to a static site.
- For a password, redirects, maintenance, or a single-page app, see Password, redirects, and maintenance.
To update later: upload another ZIP, preview, then publish again. When you need to, roll back to an older version that is still kept (about the last 3 successful releases).
How this differs from the CMS site
| CMS site | Static site | |
|---|---|---|
| How you change content | Page editor, news, and similar | Edit the HTML, then upload a ZIP |
| Address | site.timtech.tw, or the main site’s custom domain | code.sites.timtech.tw, or that static site’s own domain |
| Menu and theme | Header and footer in the admin | Everything lives in the ZIP |
| AI chat knowledge | Published pages are indexed | Not added to the knowledge base |
| Payments | The commerce module | Do not wire a separate checkout into the static HTML |
Tracking: a published static page reuses the main site’s GTM / GA4 from Set up tracking and verification. Do not put tracking snippets in the ZIP. Preview pages do not get tracking.
Related
- How modules are turned on
- Members, in brief
- Attach a custom domain (the CMS site’s domain; separate from this module)