> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/knowledge-management/docs/concept-docs/purpose-of-docs.md).

# Purpose of Docs

## Purpose and Mental Model

The purpose of Motion Docs is simple: to help you move from **raw ideas** to **polished writing** without switching tools or breaking focus. Docs give you a single environment where exploration, drafting, and refinement happen in one flow.

**Mental Model:**

* **Docs as a workspace** → Think of Docs as both a whiteboard and a writing desk. You can brainstorm freely, then refine into clear prose — all in the same space.
* **Two modes of work:**
  * **White space** for brainstorming and structuring ideas.
  * **AI co-writer** for drafting, editing, and revising text.
* **Flow, not silos** → Ideas captured in the white space flow naturally into writing, and AI helps you polish without ever leaving your doc.

**Key idea:** Motion Docs aren’t just a text editor — they’re a dynamic environment designed for the full lifecycle of content, from messy first thoughts to finished output.

## How to Think About the Workflow (Your Process)

From a user’s perspective, the value is in *how you move between the two tools*. Treat them as stages in your writing process:

1. **Explore in the white space** → Capture messy ideas, collect references, and map structure.
2. **Decide** → Clarify your direction and the message you want to communicate.
3. **Draft in AI Docs** → Turn your structured ideas into full text with AI co-writing and quick edits.
4. **Refine** → Review, revise, and finalize with version history and references.

This is the *mental model* — a loop you control. Canvas gives you freedom to think broadly; AI Docs gives you focus to publish confidently.

## What Motion Docs Is (and Isn’t)

{% tabs %}
{% tab title="What it is" %}

* A single space to **brainstorm, draft, and refine** your work.
* A combination of **flexible white space** and an **AI co-writer** that adapts to your workflow.
* A living document where ideas, structure, and polished writing all coexist.
* **A connected workflow** where you brainstorm, refine in AI Docs, and keep everything in one document.
* **A thinking companion** designed to accelerate your process, not replace it.
  {% endtab %}

{% tab title="What it isn’t" %}

* ❌ Not just a static text editor — Docs are designed for flow, not rigid formatting.
* ❌ Not a generic chatbot — AI works in the context of your document, not outside of it.
* ❌ Not a publishing CMS — Docs help you create and refine content, but publishing/distribution lives elsewhere.
* ❌ Not a replacement for judgment — AI assists with writing, but your voice, expertise, and decisions guide the outcome.
  {% endtab %}
  {% endtabs %}

{% hint style="info" %}
**Key idea:** Motion Docs are purpose-built for creating, not just storing text — giving you a space where exploration and execution happen together.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.usemotion.com/help/knowledge-management/docs/concept-docs/purpose-of-docs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.