Dreamstate documentation

Guides for setting up Dreamstate, writing posts, matching voice, scheduling content, managing workspaces, using templates, and connecting developer surfaces.

What the docs cover

These docs explain the operational parts of Dreamstate: account setup, voice profiles, the AI writing workflow, saved inspiration, post structure, publishing, templates, team workspaces, billing, and developer surfaces.

They are written for founders, operators, agencies, and marketers who need to turn Dreamstate into a repeatable growth workflow. Each guide covers the job to be done, the setup sequence, what the system stores, and the handoff into publishing, outreach, or AI visibility work.

Use the docs when onboarding a new workspace, preparing a teammate to review content, connecting a publishing channel, or deciding which part of the product owns a workflow. The public HTML mirrors the product model so search engines and AI agents can understand the docs without client-side rendering.

Recommended path

  • Start with What is Dreamstate? for the product model.
  • Read Core Concepts before setting up voice profiles and workspaces.
  • Use Writing Posts, Bookmarks & Inspiration, and Content Structure when building the content workflow.
  • Use Scheduling Posts and Multi-Platform Publishing when moving from draft to calendar.
  • Use API Reference and MCP Server when connecting Dreamstate to external automation.

How teams use the docs

A typical implementation starts with workspace setup, then voice capture, then content creation, then calendar and publishing rules. Teams with multiple contributors should read team members, workspace settings, and subscription plans before inviting users so account ownership and approvals are clear.

Teams using Dreamstate for AI visibility or warm outreach should also review the developer surfaces. The API and MCP docs explain how external systems can read workspace context, trigger approved workflows, and keep automation scoped to the correct customer account.