> For the complete documentation index, see [llms.txt](https://docs.shop-studio.io/shopware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shop-studio.io/shopware/extensions/blog/create-and-publish-posts.md).
# Create & publish posts
Blog posts are intentionally structured very similarly to regular products. This means that the creation and publication requires almost the same steps.
## Create post
You can create posts in the admin under `Catalogues > Blog posts` by clicking on the button `Create post`. It is important that you give the post a name, of course, because it is a mandatory field. Afterwards you can click on the button `Save` to save the post.
Now you can write your content for the post via the tab `Content`.
## Publish post
Creating a post is not enough to display it in the storefront. Apart from the one-time setup the following points must be in place:
* The blog post must be active.
* The blog post must have a main category OR a category.
* The blog post must be associated with a sales channel.
If everything is correct so far, the blog posts should appear in the storefront. Have fun writing them!
---
# 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://docs.shop-studio.io/shopware/extensions/blog/create-and-publish-posts.md?ask=&goal=
```
`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.