Site Builder
Edit your site's templates, layouts, scripts, styles and public files directly in the browser.
Site Builder is where your site's code lives: a template for each model, the layout that wraps every page, your scripts and styles, and public files. It's for developers and anyone comfortable with HTML.
TipMost changes don't need Site Builder. Ask the AI Assistant to change a design, or connect your own AI client over MCP for bigger jobs. Use Site Builder when you want to see or edit the code yourself.
How a page is rendered#
Each page is built from its content and its template, then wrapped in a layout:
- Templates are written in EJS: HTML with
<% %>tags for logic and<%= %>to output content. The page's content is available asitem, likeitem.hero.headline - Tailwind CSS classes are compiled for the whole site by default. You can also load other libraries, like Bootstrap. See Builder settings
- Helpers like
img(),getEntry()andtitle()do the common jobs: see the Template & helper reference
The editor#
The sidebar lists one template for each model (Entries, Pages and Blocks), then Layouts, JS Files and CSS Files, each with + Add New.
- Template · Context · Preview
- Update using AI
- Revert to older version
- Prettify code
- Tailwind CSS is enabled
- Content model · Split view · Full screen
- One template per model: Entries, Pages, Blocks
- Template, Context, Preview: the code, the data it receives, and the rendered page
- Revert to older version: bring back an earlier version of this one file. Nothing else changes
- Prettify code: tidy up the formatting
- Content model: jump to the model this template uses
- Split view: the template next to the Preview or the Context
- Full screen: more room to work
- Split view: template + preview (or + context)
- Live preview of the page
Context and helpers#
Context shows exactly the data your template receives: item (this page's content), plus entries, pages, images and options. Search it, switch between a tree and raw JSON, and copy a path like item.hero.headline straight into your template.
- item, entries, pages, images, options
- Search; tree or raw JSON
- Copy a path, e.g. item.hero.headline
Below the data is a built-in reference for every helper, grouped as Rendering, Access Content and Head / Meta, each with what it does and a copy-ready example.
- Rendering and content helpers
- What it does and its arguments
- Copy-ready examples
Preview#
Preview shows the rendered page without leaving the editor, with a device switch, zoom, the page path and refresh.
- Device, zoom, path, refresh
Layouts#
A layout is the shell around your pages: the <head>, fonts, favicons, scripts, and usually the header and footer. Each page's content goes where the layout has <%- main %>. A site can have several layouts, and each model uses one of them. We recommend keeping to one: it keeps your site simple, especially when the AI Assistant is making changes.
- Page Layout: open the layout this model uses
<%- main %>: where the page body goes- head: title, meta, links, styles
The layout is also where you add third-party scripts and libraries that every page needs. See Analytics & cookie consent.
JS and CSS files#
Add your own scripts and stylesheets, like /js/meal-plans.js, with + Add New. They have the same tools as templates: revert, prettify and save.
- Same tools: revert, prettify, save
Public files#
Public holds files that are served as they are from your site's root. Upload a file to / and it's available at yourdomain.com/<file>. Use it for:
- Documents to link to, like
/catering-menu.pdf - A favicon, or a verification file another service asks you to upload
- A custom
robots.txt, which replaces the one SleekSite creates. See SEO / AEO
- Folder tree: e.g. /catering-menu.pdf
- New folder · Delete
- Drag and drop, or Upload files
Saving and publishing#
Click Save to keep a change. Your site rebuilds the next time you open Preview, so you can check it there, and it goes live when you publish. Every preview with new changes also saves a version of the whole site in Version history.