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 |
| 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).
- Start with core routes (posts, categories, tags).
- Enable optional extensions incrementally (comments, reactions, bookmarks, stats, translations, sitemap).
- Keep runtime config and docs aligned.