> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/blog/create-and-edit-blog-posts/posts.md).

# Posts

Found under **Administration → Content → Blog → Articles**.

## Listing

The list shows every article with its internal name, status, title, author and display date. Use the filters at the top to narrow down by status, author, category or tag; the search field covers title, subtitle and short description — language-aware.

Selected articles can be activated, deactivated or deleted as a bulk action.

## Create a new article

A new article is always created in your shop's **default language**. This is a Shopware constraint: some required fields (e.g. the title) must exist in the default language, otherwise the article cannot be saved. The language picker is therefore disabled while creating.

Once the first save has gone through you can switch into any translation — see [Multilingual](/en/plugins/blog/translations.md).

## Tabs of the detail form

### Basics

Three cards:

* **Management** — internal name and status.
* **Article** — title, subtitle and short description (all translatable).
* **Display** — layout (overrides the default from the plugin configuration) and preview image.

### Content

Here you compose the actual article in the visual editor — sections, blocks, text snippets, images, galleries and so on. The full workflow incl. drag & drop and the block library is in [The content editor](/en/plugins/blog/create-and-edit-blog-posts/content-editor.md).

### Visibility

Three cards:

* **Publication** — start date (when the article becomes visible), end date (when it disappears again), display date. With the premium *Auto-publish* feature the system flips the article on and off at exactly those moments.
* **Categorisation** — categories, tags, author.
* **Sales channels** — which channels see the article. Empty = visible in every channel where the plugin is active.

### Products

Linked products appear in the article as a "Products for this article" carousel. Perfect for cross-sell: a magazine article on a topic links straight to the matching products in the shop.

### SEO

* **Meta title** — when empty, the shop uses the article title.
* **Meta description** — when empty, the short description is used.

Both fields are translatable.

## Saving

When you click **Save** the editor first checks that every required field is filled. If something's missing, the view jumps to the tab of the missing field and highlights it red — no guessing what's still incomplete.

In a translation language, required *translatable* fields are not enforced. You can save an incomplete translation; empty fields fall back to the default language in the shop automatically.

## Status

| Status        | Meaning                                                                                    |
| ------------- | ------------------------------------------------------------------------------------------ |
| **Disabled**  | Not visible in the shop.                                                                   |
| **Draft**     | Still in progress, not visible either.                                                     |
| **In review** | Waiting for approval (workflow status), not visible either.                                |
| **Active**    | Visible in the shop — provided the start date has passed and the end date is not exceeded. |

> With an active premium licence the plugin flips the status automatically based on the start and end dates. In the Basic and Advanced plan you set the status manually.

## Delete an article

Deleting removes the article along with every translation, all content, every category / tag / sales-channel / product link and every review. Preview images and media used inside the content stay in the Shopware media library.


---

# 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.premsoft.de/en/plugins/blog/create-and-edit-blog-posts/posts.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.