Skip to content
On this page

Blog Module ​

The Blog module adds a complete content layer on top of Flowless auth.

This page explains what is core, what is optional, and how to understand extensions without confusion.

Core vs Extensions ​

AreaTypeRequired to use Blog?Notes
Posts (CRUD + publish/unpublish/schedule)CoreYesMain content workflow
Categories and tagsCoreYesBasic content organization
CommentsCoreNoCan be disabled per product policy
ReactionsExtensionNoOptional engagement layer
BookmarksExtensionNoOptional user utility feature
Views and statsExtensionNoOptional analytics surface
TranslationsExtensionNoOptional multilingual support. Language codes are listed in Languages.
SitemapExtensionNoOptional SEO automation
Featured image uploadExtensionNoOptional media enhancement

Friendly rule ​

Use Blog Core first, then enable extensions only when the product really needs them.

Extensions are not mandatory. For example, reactions can stay disabled and Blog still works correctly.

Activation flow ​

  1. Install Blog from Module Hub (usually via Pubflow Platform asset console).
  2. Turn the routes on with BLOG_ENABLED=true. Until then every blog route returns 503 MODULE_DISABLED. The server default is false.
  3. Start with core routes (posts, categories, tags).
  4. Enable optional extensions incrementally (comments, reactions, bookmarks, stats, translations, sitemap).
  5. Keep runtime config and docs aligned.

GLOBAL_LANG is only the language of emails and system messages (en, es, fr). It does not enable the blog and it does not set a post's language.

VariableDefaultWhat it does
BLOG_ENABLEDfalseOpens the blog routes
BLOG_I18N_ENABLEDfalseOpens translation create/update/delete. A post can still store lang, for example "es", while this is off
BLOG_DEFAULT_LANGenLanguage used when create omits lang
BLOG_MCUemptyOne URI that overrides the separate BLOG_* flags when it is valid. Example: blog://enabled@config/v1?i18n.enabled=true&i18n.default_lang=en

Post Types is a second switch. The blog works without it. See Post Types. Installing that schema does not enable /api/v1/post-types; set POST_TYPES_ENABLED=true (or POST_TYPES_MCU=post-types://enabled) after the blog is on.

Read the API docs ​