Documentation that matches the product
Clear, structured documentation for installing, configuring and extending ModularPress. Written for real projects, not demo setups.
- Product concepts explained without buzzwords
- Modules documented the same way they appear in the admin
- Examples based on real use cases
Start with the fundamentals
The documentation follows the same mental model as the product itself. You start with core concepts and build up towards modules, workflows and integrations.
Core concepts
Learn how ModularPress structures content, users and configuration. This section explains how modules, pages and permissions fit together before touching advanced features.
Start here if you are new to the product or planning your first setup.
Modules
Each admin module is documented as an independent building block with a clear responsibility and scope.
Module documentation matches the structure you see in the Modules section.
Configuration
Installation, environment setup and system level settings explained step by step.
Includes database structure, permissions and deployment considerations.
How the documentation is organized
Product overview
High level explanation of how ModularPress works as a system. Covers the admin philosophy, module separation and long term scalability.
Closely related to the Product page.
Module reference
Detailed documentation for each module available in the admin. This includes Users, SEO, Menus and others.
Each module page explains purpose, data model and common workflows.
Use case driven guides
Practical guides built around real workflows such as websites, client portals and internal tools.
These guides align with the pages in Use cases.
Who the documentation is written for
Developers
Understand the data model, module boundaries and extension points without reverse engineering the codebase.
Learn how modules interact and where custom logic belongs.
Editors and content teams
Learn how posts, pages, menus and publishing workflows work without technical noise.
Closely tied to modules like Posts, Categories and Menus.
How to use this documentation
Documentation is not meant to be read top to bottom. Use it as a reference while working in the admin.
- Start with the product overview to understand the system
- Read module documentation when enabling or using a new module
- Use use case guides to plan real world setups
- Return to configuration docs when deploying or scaling
Looking for something specific
If you cannot find what you need in the documentation, the best next step is to explore the modules directly or ask us.
