Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
You can create your own modules for Magnolia. The best practice is to package your entire website project, including customized templates, components and content, into modules for easy deployment. In this section you find the set of tools required for development. If you have experience developing webapps, you should be able to apply them to any platform.
- Magnolia front-end development
- Light development in Magnolia
- YAML
- API — These are the essential interfaces and classes in the Magnolia API.
- Bundles and webapps
- Commands — Commands can perform duties within the system or connect to external resources.
- HTTP and JCR session debugging — HTTP and JCR session debugging.
- Definition decoration
- Development environment — Developing with Magnolia requires a minimal set of tools.
- Integration — Options for integrating other systems to Magnolia.
- Resources
- Reusing configuration — A definition item is a configuration of a "component" to execute tasks in a Magnolia instance. Template definitions, dialog definitions, app definitions (also known as app descriptors), renderer definitions, themes definitions, field definitions are all examples of such definition items. They can be configured via JCR in the configuration workspace.
- Creating a website with Magnolia
- Accessing content on the client side
- How to add an asset with REST
- How to get content as JSON - an overview
- How to create a custom Java-based REST endpoint
- How to work with JavaScript models
- Best practices
- Tips and tricks to hack
- BOM for third-party modules
Overview
Content Tools