Skip to content
Resources · Roadmap

Where ModularPress is heading

A realistic roadmap focused on long term stability, predictable growth and real project needs.

  • No feature hype
  • No broken promises
  • Direction over deadlines

Planning with intention

The roadmap explains where ModularPress is going and why. It reflects real usage, feedback from running projects and lessons learned from maintaining long living systems.

Completed work is documented in the changelog. This page focuses on what is next and what is being evaluated.

Stability first

Core behaviour and data structures are treated as long term contracts. Changes are incremental and documented before they ship.

Modules over features

New capabilities are added as focused modules instead of expanding existing ones beyond their responsibility. See the current modules.

Feedback driven

Roadmap priorities are influenced by real projects, not theoretical use cases or trend chasing.

How roadmap items are categorized

Each item on the roadmap belongs to one of the following states. This helps set clear expectations.

In progress

Actively being developed. Scope is defined and work is ongoing. Changes from this stage will appear soon in the changelog.

Planned

Scheduled for future releases. Direction is clear, but exact implementation may evolve based on testing and feedback.

Under consideration

Ideas being evaluated. These items may change, move forward or be dropped if they do not align with the core philosophy.

What appears on the roadmap

  • New modules or major module expansions
  • Admin workflow improvements
  • Security and permission model refinements
  • API and integration related changes

Minor bug fixes and internal refactors are documented only in the changelog, not tracked here.

Who this roadmap is for

Project planners

Decide whether upcoming capabilities align with your project timeline and scope.

Developers

Understand where the platform is heading before committing to custom extensions.

Long term users

See how ModularPress evolves without unexpected direction changes.

Follow progress transparently

Planned work becomes real only once it ships. Track completed changes and release notes in the changelog or dive deeper into how things work in the documentation.