Your first site
1. Create a site
Section titled “1. Create a site”In the portal, choose the Organization and select New site. You can also ask an authenticated AI agent to create one using an organization-scoped key. A site-scoped key cannot create other sites.
You do not need GitHub, Cloudflare or a custom domain to start editing.
2. Add content
Section titled “2. Add content”Choose the Site, open Pages and create a page. Open it in the visual editor to add blocks and edit their fields.
With an AI agent, describe the site and the work you want it to do. For example:
Create a small website for a landscape design studio: Home, Projects and Contact.Use our existing site settings, header and footer. Build editable blocks.Keep the pages as drafts and show me a preview before publishing.The agent uses your site’s settings, blocks, templates and API tools. If it works
with multiple sites, have it confirm the selected Site and Version before changes.
The bundled tr-new-site recipe is optional; clients load recipe files differently.
3. Review and save
Section titled “3. Review and save”Open the editor’s Publish menu and use Review changes to compare the working copy with saved content. Select Save when the changes are ready.
For an agent-created preview, request include_working_copy: true to include
unsaved changes. A normal preview shows saved CMS content, which can differ from
the last public deployment. Expiring previews do not publish a permanent site.
Check navigation, text, image alt text and the mobile layout. Use the editor to correct content or ask the agent to make a specific change, then save it.
4. Set up publishing
Section titled “4. Set up publishing”Open Account → Publishing. An organization owner or admin completes the account and domain setup and selects the build provider. The Site uses its assigned Hosting Group for static hosting.
The site’s default address is under that group’s configured site address base.
New customer-publishing sites do not get a permanent typeroll.com subdomain.
5. Publish the saved version
Section titled “5. Publish the saved version”Select the intended Version. In Publish, set ready pages to Published,
then select Deploy. Review the changes listed beneath the deploy control.
The agent equivalent is to save content, set its status and call trigger_deploy.
Wait while the build and distribution are verified. The public link appears automatically when the deployed artifact is available. A saved Published status alone does not mean the page is live.
The main version is the live branch; other versions use separate branch
addresses with noindex. See Deploy tools.
Next steps
Section titled “Next steps”- Prepare your website and media domains.
- Add Forms and verify a submission before sharing the site.
- Check SEO and indexing.
- Run the CMS yourself.