> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/web-app-features/inspiration/remix-posts.md).

# Remix Posts

## Remix Content

Open Tools > Inspiration to find a post to adapt.

1\. Click "Remix" on the bottom of the post you like.

2\. Blotato will generate an adapted version of the post while keeping the essence intact.

3\. You SHOULD add your personal touch, experiences, stories, etc. Add your unique POV.

4\. Use Chat to make quick edits.

If Remix opens the older editor, follow its controls. To write in Content Studio instead, open Post editor, add the example as Text under Context, and describe your requested adaptation. See [Create posts](/web-app-getting-started/posts.md).

## FAQ

### Q: If you don't have much context in your industry or niche, how do you use the Remix feature?

Open Content Studio > Post editor, select Add context source, then choose Perplexity. Enter the topic to research and wait for extraction. Review the source before asking for a draft. See [Context](/web-app-getting-started/sources.md).


---

# 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://help.blotato.com/web-app-features/inspiration/remix-posts.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.