What is a headless CMS?

A headless Content Management System (CMS) is a backend system that acts as a content repository. It enables organizations to create and manage content once and then serve it to any frontend such as websites, apps, and even VR headsets. While a headless CMS does not have a built-in presentation layer, a hybrid-headless CMS offers APIs and page rendering capabilities, offering the best of both worlds. Some headless CMSs also offer WYSIWYG editors , enabling content authors to create digital experiences visually.

A headless CMS enables a company to create and manage content once and then publish it to any device or touchpoint without restrictions. It doesn't force any templates or themes onto the content created within it. Instead, APIs are used to deliver the content to any frontend such as websites, apps, digital signage, smartwatches, or VR headsets. The approach increases flexibility and efficiency and helps brands provide an innovative customer experience on desktop, mobile, or any other connected devices.

What is headless commerce?

Headless commerce refers to a decoupled architecture that separates the ecommerce platform in the backend from the storefront. A headless Content Management System (CMS) is often part of the headless commerce stack too. The frontend, i.e. the storefront, consumes product data and content via APIs . This allows brands to manage the backend and the presentation layer independently, increasing flexibility and efficiency. Composable commerce takes headless commerce a step further and allows for other services to be easily integrated.

Jan 9, 2026
--

Streamlining the developer experience with the new Magnolia CLI version 5

Martina Michlova
Senior Front-End Solution Architect, Magnolia

Core pillars of CLI version 5
Technical capabilities and code generation
- Framework integration and starter projects
- Component library and styling
Solving infrastructure friction
Managing data and legacy projects
Conclusion
Try the Magnolia CLI v5 today
FAQ

Experience Magnolia in action

Experience Magnolia's key features firsthand in an interactive product tour.

Take a tour now

Key insights

Unified tooling: CLI version 5 replaces legacy tools and the Headless Accelerator with a single, standardized tool for both headless and FreeMarker projects.
Rapid onboarding: New "jumpstart" capabilities and starter projects allow developers to spin up ready-to-run templates in major frameworks like React, Vue, and Next.js.
Infrastructure flexibility: A new docker start command enables developers to run Magnolia without a local Java setup, solving a major friction point.
Extensible architecture: The tool is built on a plugin based architecture, allowing teams to create custom workflows while maintaining standardization.

For development teams, speed and consistency are often at odds with each other. The new Magnolia CLI version 5 addresses this friction directly. It is a unified, plugin-based, and standardized command-line interface designed to accelerate development and resolve project fragmentation.

Previously, developers navigated two separate tools: CLI version 4 for FreeMarker projects and the Headless Accelerator for headless implementations. This split caused inconsistent setups and slowed down onboarding. Version 5 eliminates this dichotomy, providing a single, modern tool that streamlines the developer experience regardless of the underlying technology stack.

Core pillars of CLI version 5

The architecture of the new CLI is built on three fundamental concepts designed to professionalize the development workflow:

Unified CLI: A single entry point for both headless and FreeMarker projects. This simplifies onboarding by establishing one workflow for all developer types.
Plugin-based architecture: Every feature functions as an isolated plugin. This ensures flexibility and maintainability, allowing developers to adapt the tool to specific project needs without altering core functionality.
Standardization: The tool enforces consistent structures and naming conventions across teams. While it promotes best practices out of the box, it remains flexible enough for teams to implement custom standards via their own plugins.

Technical capabilities and code generation

The primary function of the Magnolia CLI version 5 is code generation that aligns with recommended practices. It automates the creation of components, pages, and content types, significantly reducing manual configuration.

Framework integration and starter projects

The CLI seamlessly integrates with major front-end frameworks. It provides "starter projects"—consistent, ready-to-run templates—for the following technologies:

React
Vue
Angular
Next.js
Nuxt
Angular SSR
FreeMarker

These starters are not just empty shells; they are preconfigured to handle the integration and communication between the front-end application and Magnolia automatically. They also showcase advanced features out of the box, such as component autogeneration and personalization.

Component library and styling

To further accelerate development, the CLI includes a component library providing reusable base components (such as accordions, cards, and heroes).

Full ownership: When a developer generates a component, the code is copied directly into their codebase, granting full control for customization.
Automated file generation: The create component command generates all necessary files at once, including the dialog definition (YAML), template definition, and the front-end implementation (e.g., hero.js).
Styling: Default components come with Tailwind CSS styling, though they can be rendered without it if preferred.

Solving infrastructure friction

A significant enhancement in version 5 is the removal of local Java dependencies for front-end developers.

Docker start: The new docker start command allows developers to start Magnolia without installing or configuring Java locally.
Parallel projects: Developers can run multiple projects in parallel using Docker by manually assigning unique ports to each instance, ensuring completely separated environments.
Watch mode: The tool monitors specific file paths and automatically triggers relevant plugins upon change, enabling rapid feedback loops during development.

Managing data and legacy projects

The CLI is designed to support both greenfield projects and existing implementations.

Legacy integration: The init command allows existing projects—even those created with the legacy CLI v4 or Headless Accelerator—to connect to and benefit from CLI v5 features.
REST endpoint generation: The tool supports template generation for REST endpoints. Crucially, if references to other workspaces exist, the CLI automatically includes preconfigured reference resolvers, ensuring the API delivers resolved content right away.
Customization: For teams with specific needs, the "Jumpstart" plugin supports custom project templates. Users can define their own templates to specify exactly which bundles and versions are initialized.

Conclusion

Magnolia CLI version 5 represents a shift toward a "unified and accelerated" development model. By officially deprecating the Headless Accelerator and unifying workflows under one extensible tool, Magnolia ensures that developers spend less time on manual setup and more time building high-value digital experiences.

Whether you are building a headless CMS project with modern front-end frameworks or a traditional server-side rendering implementation, the new CLI provides the standardized foundation necessary for modern enterprise development.

Try the Magnolia CLI v5 today

Magnolia CLI v5 is built to empower developers, offering a unified and customizable tool that supports both Freemarker and headless projects.

Ready to experience the power of a unified CLI that evolves with your needs?

Check out our CLI documentation and start exploring all the possibilities. We’re excited to see what you’ll create with it.

Try the Magnolia CLI v5 today and take your development process to the next level!

FAQ

Currently, the CLI does not enforce a hard limit on the number of references created in a REST endpoint. However, it is recommended to validate complexity and reference depth to prevent potential performance issues in large projects.

Yes. Using the docker start command, you can run multiple isolated projects in parallel. You simply need to configure different ports for each instance to avoid conflicts.

You can use the init command provided by CLI v5. This command ensures that existing projects, including those built with legacy tools, can connect to the new CLI and utilize its features without rebuilding from scratch.