Sites and domains
Maestro hosts static sites. You ask Claude to build one, it deploys, and the
files are served from disk at https://<slug>.sitesmojo.com — or at a domain
you control.
There is no build step. No npm, no bundler, no server-side rendering. HTML, CSS
and a little vanilla JavaScript if the page genuinely needs it.
Publishing is immediate and public
This is the one thing to internalise before you start. A deploy is queued and a
worker flips it live within seconds. There is no staging and no private
preview — once it lands, the page is public at the site's address to anyone
with the URL.
Two habits follow from that:
- Pick the slug carefully. It is the URL and the path on disk, and it cannot
be renamed after creation. - Ship a root
index.html. Without one,/returns a 404 — the deploy reply
warns about exactly this, so read it.
Mounting a documentation book
A book is content you write in markdown from chat; mounting it on a site
renders it as static pages. One book at /docs, another at /blog. Choose the
presentation with kind:
docsandwikirender hierarchical navigation and a tree index.blogandnewsrender a reverse-chronological index plus tag pages, year
archives and an RSS feed.
Mounted pages get a topbar, sidebar navigation, breadcrumbs, prev/next links,
anchor links on headings, copy buttons on code blocks, light and dark, and a
client-side search box over the section — none of which you write. Everything is
inline, so the pages load nothing from any third party.
A mount is never at the site root. If your bundle ships no root index.html,
one is generated that redirects to the first mount.
What rollback does and does not do
Rolling a site back rewinds the site's own files. Mounted book content
always re-renders at the book's current published state, so a rollback cannot
resurrect a page you unpublished or an older wording. To rewind book content,
restore that page's revision and republish it.
Your own domain
Attaching a hostname gets you HTTPS, issued and renewed automatically once DNS
points at the platform. The full walkthrough, including the records to publish
and what each state means, is in
Attaching a custom domain.
Files the platform adds for you
Every deploy adds robots.txt and sitemap.xml, generated from your pages with
absolute URLs on the live hostname. Sites with mounted books also get
llms.txt and llms-full.txt, plus a .md mirror of every page.
Ship your own file at any of those paths and yours is kept untouched. That
is the opt-out — there is no flag to set.