Low-code Development

Simplify and speed up development with Magnolia using file-based configuration.

Low-code Benefits

Go faster

Every change to your configuration is applied instantly. Hot deployments mean no compile, no restart, no waiting.

 

Work your way

Magnolia’s file-based configuration enables you to work in the comfort of your favorite editor, IDE, and tooling.

 

Customize without Java

Magnolia is a Java CMS, but Magnolia’s low-code development allows you to implement projects with a front-end skillset.

 

Develop Faster with Magnolia

Magnolia’s low-code development helps you deliver experiences faster. It is mainly based on YAML files to configure Magnolia resources and functionality on the fly. This approach does not require Java skills or a Java development environment, making it fast and easy to adapt Magnolia to your needs.

Our file-based configuration also allows you to use your existing tools and workflows to control your CMS. For example, you can store your entire configuration in git, providing transparency, repeatability, and a great development experience.

YAML Makes the World Go Round

Magnolia monitors its file system and responds to changed or new configuration files immediately. The configuration that can be changed using YAML includes Content Types and Apps, REST endpoints and clients, templates and dialogs, content language, and redirects. Other options such as system internationalization can be configured using plain-text configuration files.

Configure APIs for  delivery and integration

Create API endpoints such as delivery and GraphQL endpoints to enable headless content delivery and automation

 

Manage custom Content Types and Apps

Define the key types of content in your project by creating a content model called Content Type. Then create a Content App based on the model to allow content authors to easily create and manage content via the GUI.

 

Create forms for content creation and management 

Enable your content authors to create and edit content using forms, called dialogs, whether you use Magnolia to render pages or choose to deliver content via APIs.

 

Create page components and templates

Simplify templating by writing page and component definitions in YAML and HTML. Your content authors and marketers can use these templates to build experiences in the visual editor.

 

Make content available in different languages

Configure which dialog fields contain translatable text to enable internationalization or create a project-specific dictionary by adding configuration files containing website copy and its translations.

 

Customize Magnolia’s authoring experience

Give Magnolia’s AdminCentral your look and feel by changing the names, icons, and location of apps. You can also change the system language to match your authors’ preference.

 

Read the Tutorial

Light Modules

Config files are packaged in simple and consistent folders on the file system called ‘light modules’.

Magnolia CLI

Magnolia has a command line interface (CLI) to trigger and automate frequent tasks such as starting and stopping Magnolia, generating the configuration folder structure, and generating key YAML definitions. The CLI makes it even easier to manage Magnolia and prevents errors.

Learn more about our CLI

% mgnl -h
Usage: mgnl <command> [options]
A tool to setup and facilitate light development with Magnolia CMS
Options:
-v, --version output the version number
-h, --help output usage information
Commands:
jumpstart download and setup a Magnolia CMS instance for development.
start start up a Magnolia CMS instance. To stop it, enter CTRL+C
add-availability add component availability.
build scan a node_modules folder for npm packages with the keyword "magnolia-light-module" (in package.json) and extract them to a directory of choice.
create-app create an app.
create-block create a block.
create-component create a component and optionally add availability for it.
create-content-type create a content type.
create-light-module create a light module.
create-page create a page template.
create-virtual-uri create a virtual uri mapping.
customize-local-config extract "mgnl-cli-prototypes" folder and "mgnl-cli.json" file to customize CLI configuration.
install install a light module from npm to the local Magnolia instance.
search search for a light module on npm.
tab-completion install tab autocomplete feature for Bash, zsh or PowerShell
version display mgnl and node.js versions
help [cmd] display help for [cmd]

More Resources

All Resources
Whitepaper CMS
Magnolia in a Can: Containerization with Magnolia

Learn how to deploy Magnolia as a Docker container based on best practices from our professional services team

Magnolia in a Can - Containerization with Magnolia
Cloud and Self-Hosted Deployment

Choose Magnolia’s Platform-as-a-Service for fast and easy deployment, or host your own Magnolia instances for maximum flexibility

Cloud and Self-Hosted Deployment
Building DX

Create truly amazing digital experiences using the frontend technology you love and getting the content flexibility you need.

For Developers
Sign-up for a Developer Trial

Experience all that Magnolia has to offer with our enterprise-grade DX Core trial: multi-site, multi-source, personalization, tagging, workflows and more.

Magnolia Developer Trial

Sign-up for a Developer Trial