Skip to content

Blog

Why a PIM has a blog, how it connects to the catalogue, and what the module adds.

Requires the module Blog
On this page

A blog inside a product-data system is not a detour. The articles are here because they know the catalogue: they can refer to a specific product, category or brand, and when the product changes the reference in the article still holds.

The blog section with its own left menu and the dashboard
Fig. 1 The blog section. The menu runs in the order content is created: topic → author → article.

Controls on this screen

  1. DashboardThe automation overview. This is where you see whether the blog is writing itself.
  2. ArticlesEverything produced — drafts awaiting review included.
  3. CategoriesTwo levels: a group and the categories inside it.
  4. TopicsThe pool of briefs. Without topics, AI authors have nothing to write about.
  5. AuthorsA byline and a schedule. An AI author is what sets the blog going.
  6. TagsA flat list of themes cutting across categories.
  7. SettingsThe master automation switch, the translation languages, and whether articles publish straight away.

How it works

  1. A topic

    An idea reaches the topic pool — either you add it, or the system proposes it from the catalogue.

  2. An article

    The topic becomes an article. You write it, or have it generated and then edit it.

  3. Filing

    The article gets a section, an author and tags.

  4. Publishing

    It appears in the shop at an address derived from its section and title.

The chapters in this section

ChapterAnswers the questionNote
Blog overviewWhat is in progress and what awaits approval?
ArticlesHow do I write, edit and publish an article?Including links to products.
Topic poolWhere do the ideas come from?The heart of the automation.
SectionsHow are articles grouped?
AuthorsWhose name is on the article?
TagsHow do I label across sections?
Blog settingsHow often, how long, and in what tone?Including the approval mode.