Guides

Mini Agency guides are written for creators who build and operate sites in the editor. They follow the product surfaces in the order you normally meet them: workspace, pages, editor, content, publishing, and account settings.

Start here

If you are building your first site, read Getting started first. It explains the shortest path from a new workspace to a live staging page. Then read The editor so the canvas, left rail, right rail, and breakpoint controls make sense before you make large edits.

If you already have a site, jump to the workflow you are doing now:

• Pages and navigation for slugs, home page, menus, visibility, and SEO basics.
• Design system for shared colors, fonts, classes, and responsive rules.
• Components and instances for reusable headers, footers, cards, and sections.
• Collections and CMS for structured content, listing pages, and single item templates.
• Forms for form fields, submission actions, privacy consent, and testing.
• Media for uploads, AI-generated images, reuse, alt text, and cleanup.
• AI chat and agents for safe assistant-driven edits.
• Publishing, domains, and exports for staging, production domains, DNS, and static exports.
• Account and billing for plans, invoices, limits, and payment settings.

How these guides are written

Each guide is operational. It tells you what to click, what state to check, and what can break. Mini Agency is powerful because the same document powers the canvas, public renderer, AI agents, forms, and MCP tools. That also means a small change can affect several surfaces. The guides call out those boundaries explicitly so you can work confidently.

Before you publish

Use this short checklist whenever you are preparing a site for a client or public launch:

• Every page has a clear title, slug, and meta description.
• Navigation links point to existing pages.
• Desktop, tablet, and mobile breakpoints have been previewed.
• Repeated sections are components instead of copied markup.
• CMS listing pages and single item templates use the right collection.
• Forms have success behavior, consent copy, and at least one test submission.
• Images have useful alt text and are not broken external URLs.
• Staging access is set intentionally: workspace-only, password, or public.
• Production domain DNS is verified before announcing the site.

Related docs

• Agency docs for white-label teams managing many clients.
• Developer docs for MCP, forms, renderer, exports, and document internals.