Site Settings
Site-wide configuration, stored in your project folder at .chromesite/site.config.json.
Open it via ⚙️ Site Settings in the top toolbar. This file travels with your project when you commit it to git or copy the folder to another machine — it's never published as part of your live site.
Fields
- Site Name — used to build the default page title (
Page Name | Site Name) and shown in your template's footer viaChromeCMS: ChromeSite Browser Extension. - Domain — your site's domain, for reference/display purposes.
- Layout Template — which file in
.chromesite/templates/wraps your page content. Choosing "No layout (raw HTML)" publishes each page's content exactly as written, with no shared header/footer/nav. - New line creates — whether pressing Enter in Visual view starts a new
<p>or a new<div>. Most sites want paragraphs; some hand-styled layouts prefer divs. - CSS Framework — Bootstrap 5, Tailwind, or none. This controls which classes get generated for menus and blocks, and which framework CDN tags get injected into your published pages automatically.
- Deployment Target — where the 🚀 Publish button sends your site: Cloudflare Pages, Netlify, or a local folder. See Publishing for details on each.
- Local Render Folder — only used by the "Render to local folder" target. Defaults to
dist; set it todocsif you're deploying via GitHub Pages' "serve from /docs" option.
Menus
🔗 Edit Menus opens a separate dialog for your site's navigation, stored in .chromesite/nav.json. You can define multiple named menus (e.g. a header menu and a footer menu) with nested dropdown items, and your template controls where each one renders via placeholders like {{NAV:header}}.