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
| Area | Type | Required to use Blog? | Notes |
|---|---|---|---|
| Posts (CRUD + publish/unpublish/schedule) | Core | Yes | Main content workflow |
| Categories and tags | Core | Yes | Basic content organization |
| Comments | Core | No | Can be disabled per product policy |
| Reactions | Extension | No | Optional engagement layer |
| Bookmarks | Extension | No | Optional user utility feature |
| Views and stats | Extension | No | Optional analytics surface |
| Translations | Extension | No | Optional multilingual support. Language codes are listed in Languages. |
| Sitemap | Extension | No | Optional SEO automation |
| Featured image upload | Extension | No | Optional 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
- Install Blog from Module Hub (usually via Pubflow Platform asset console).
- Turn the routes on with
BLOG_ENABLED=true. Until then every blog route returns503 MODULE_DISABLED. The server default isfalse. - Start with core routes (posts, categories, tags).
- Enable optional extensions incrementally (comments, reactions, bookmarks, stats, translations, sitemap).
- 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.
| Variable | Default | What it does |
|---|---|---|
BLOG_ENABLED | false | Opens the blog routes |
BLOG_I18N_ENABLED | false | Opens translation create/update/delete. A post can still store lang, for example "es", while this is off |
BLOG_DEFAULT_LANG | en | Language used when create omits lang |
BLOG_MCU | empty | One 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.