Skip to end of metadata
Go to start of metadata

In this roadmap we share our product vision and make public what we plan to implement for the next major version. In the backlog we maintain potential new features. We don't share two-year plans as the CMS world changes rapidly. We believe that planning specific features beyond the next 6-12 months is not meaningful.

Product vision

We focus on five main domains in which we want Magnolia to be strong. Future releases will always include features or improvements of at least one domain.

  1. Integration and interoperability: Magnolia's strength is extensibility and its adaptability. We keep improving this domain.
  2. Usability and ease of development: We are preparing a focused effort to "lower the entry barrier" to make Magnolia easier to use for authors, admins and developers.
  3. High performance: Magnolia's client projects are getting bigger and bigger, which brings new challenges. We want to make sure that Magnolia fits the future needs of such projects. We aim to provide author instance clustering, support for clouds, content delivery networks (CDN) and snippet caching.
  4. Mobile revolution: We made a major step to mobile in Magnolia 5. We will continue to invest in mobile to maintain the headway.
  5. Marketing: We know that the marketing needs advanced functionality in a WCMS. We plan to add more marketing related features such as personalization, multivariate testing and reporting.


We work with stories and epics and maintain them in our JIRA instance. Each project and module has two special versions:

  • Backlog: stories we should implement in the next two years
  • Ideas: visions and new ideas
In addition, we have a JIRA project named Backlog in which we maintain the major epics and stories. Stories or bugs with the label 'next' are ready to be selected for the next version.

Planned major releases

When we plan a new release we select stories or epics from the backlog based on their business value and expected implementation effort. We also try to define a theme per major version and ship a meaningful bundle of features together.

The following versions are planned or in-planning:

Maintenance releases

Each project/module has a .x version for maintenance. Tickets scheduled for the next maintenance release are moved to a specific maintenance version. Tickets are selected based on the following pattern:

  1. Tickets with blocker status
  2. Tickets related to a customer support issue
  3. Tickets with the label 'next' 

Bug fix releases lists the bug fix releases and their planned release dates.

Past releases

Release notes for past releases are available on the documentation site.

  • None