Page tree
Skip to end of metadata
Go to start of metadata

Welcome to the Magnolia roadmap. On the Trello board you can see what we are working on and what is coming up next.

  • Now: items we are currently working on or have specified.
  • Next: items we have decided to do but have not yet started.
  • Later: items we are aware of but have not committed to doing.

Click the cards to learn more about any item.

The colored labels such as LIGHT DEVELOPMENT are high level themes.

Domains of strength

We focus on six 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 adaptability.
  2. Usability: Ensure that Magnolia is a joy to use and remove pain points.
  3. Ease of development: Focus on lowering the entry barrier to make Magnolia easier to use for authors, admins and developers.
  4. High performance: Make sure Magnolia can be scaled up to handle traffic peaks.
  5. Front end and headless : Make it easier for front-end developers to work with Magnolia.
  6. Business: Business needs advanced functionality such as personalization, A/B testing and reporting.

Past releases

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

  • No labels


  1. State of "tagging" and "autocomplete"?

    There are several pages within the Magnolia wiki dealing with the tagging of content (e.g. this roadmap) and about autocomplete/autosuggestion features. Are there any news about these subjects? Who would be the right person to address for further questions? There used to be a tag cloud module made by openmindlab for the 4.5 version of Magnolia - which is currently still used by some of our customers. This module had a quite useful autocomplete input field - working in some kind of Facebook style for autosuggestions. As we foresee the need for such a tag cloud module in the near future we would even consider the possibility of developing one ourselves. But could you tell us how far your developments have already reached? So - for instance - is there an autocomplete field for Magnolia? Thx in advance.

    1. Tagging: Delivered in Magnolia 5.6. 

      Auto-tagging with image recognition: Delivered with Magnolia 6.0.

      Auto-completion in configuration tree. No plans to implement at the moment. Most configuration is now doable in YAML files, reducing the time spent in the configuration tree.

  2. Regarding "Linking Content Items together", Richard Unger investigated in great detail problems and potential solutions regarding ContentViews and Chooser Dialogs. Any chance to get this on to the near future road map? Thanks!

  3. I've created the following page with questions on architecture roadmap: Architecture Roadmap

    Feedback would be highly appreciated!