> 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/cms-blocks.md). # CMS blocks PremsBlog ships a whole range of blog elements that you can place **anywhere in the shop** — not only on the article detail page. You'll find them in the Shopping Experience block library under the **"Blog"** category. ## For home page, landing pages and anywhere else These elements work on **every page type** (home, landing, category, blog). Ideal for surfacing magazine content right inside the purchase flow. ### Latest posts Shows the most recently published articles in a card grid. Adjust the number of articles in the block setting (default: 6). ### Posts by category Pick a blog category and the element shows the latest articles from it. Perfect for topic pages or category-specific campaign landing pages. ### Selected posts A hand-curated list where you decide the order. Great for editorial picks, "Also interesting" sections or a curated magazine preview on the home page. ## For the magazine overview These elements are used by the bundled "Blog listing page (PremSoft)" layout — you can also place them freely in your own layouts. ### Article list Card grid with pagination. Honours every active filter (category, tag, author, sort). ### Filter sidebar Checkbox panel for categories, tags and authors plus a sort dropdown. Updates the list instantly without reloading the page. ## For author pages * **Authors overview** — card grid of every active author. * **Author profile** — combination of photo, name and description. * **Author name**, **Author image**, **Author description** — individual building bricks for custom author layouts. * **A–Z filter** — filter bar for the authors overview. ## For the article detail page These elements read from the article currently being shown and are especially useful when you want to rebuild the default detail page to your liking: * **Title** — headline with top-category badge and meta line (author, date). * **Subtitle** * **Short description** (lead) * **Preview image** — hero image * **Author card** — photo + name + bio excerpt * **Categories** — badge list * **Tags** — badge list * **Linked products** — cross-sell carousel * **Star aggregate** *(premium)* — stars + review count + "write a review" button * **Review form** *(premium)* * **Review list** *(premium)* ## Extending in your own theme Every storefront template for the blog elements is extensible via the normal Shopware theme mechanisms. If your theme or an additional plugin adds tweaks, it can override or extend individual parts of an element with no friction. --- # 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/cms-blocks.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.