> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/marketing-studio/marketing-studio.md).

# Start here

Marketing Studio turns your company context into a content pipeline — blog ideas, drafted articles, and posts for social.

**Marketing Studio** is Dapta's content engine. You give it the context of your business once, and it produces a steady stream of content ideas, drafts them into articles, and turns the ones you approve into posts for social.

Nothing publishes without you. Every stage — the idea, the article, the post — waits for your approval before it moves on.

## How the pipeline works

| Stage           | What happens                                             |
| --------------- | -------------------------------------------------------- |
| **1. Context**  | You describe your business, your audience and your voice |
| **2. Ideas**    | Dapta proposes blog post ideas based on that context     |
| **3. Articles** | You approve an idea and Dapta drafts the article         |
| **4. Review**   | You edit or approve the draft                            |
| **5. Social**   | An approved article becomes LinkedIn posts               |

***

## Start here

{% content-ref url="/pages/pIKuqOL9NqydAqmHAbUN" %}
[Setting Up Your Content Automation with Dapta’s Marketing Studio](/marketing-studio/setting-up-your-content-automation-with-daptas-marketing-studio.md)
{% endcontent-ref %}

{% content-ref url="/pages/Frgwybnsq7hwaI9jLRed" %}
[How are content ideas created in Dapta?](/marketing-studio/how-are-content-ideas-created-in-dapta.md)
{% endcontent-ref %}

{% content-ref url="/pages/Zo4AC5Qb2ILi5fwbtfJS" %}
[Managing your blog post Ideas](/marketing-studio/managing-your-blog-post-ideas.md)
{% endcontent-ref %}

{% content-ref url="/pages/davcaxNQe3x0koFNx1in" %}
[Approving or editing your Articles](/marketing-studio/approving-or-editing-your-articles.md)
{% endcontent-ref %}

{% content-ref url="/pages/Fz55Pg88p8tUjxud0CHO" %}
[Turning your blog posts into LinkedIn Posts](/marketing-studio/turning-your-blog-posts-into-linkedin-posts.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/marketing-studio/marketing-studio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.