Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

This

...

Motivation

From:Frontend Vision - Management Overview

A Fundamental Problem

It’s handy to work on things in admincentral - but it’s an inherent anti-pattern that changes made in adminCentral are not in your “project”. 
It causes additional headaches & work:

  • You must make the same changes in your files (resources&templates). You might forget.

  • You must export changes to configuration to bootstraps. You might forget.

  • You must import bootstraps or reinstall modules. You might forget.

  • You must write module version handlers to handle the configuration changes on update.

  • You must write tests for the module version handlers.

  • The module version handlers and tests must be reviewed and qa’d.

Also the workflow for configuration is completely different then that for code, which slows down productivity.

Resources / References

Configuration by Code: Original 5 arch notes & discussion: https://docs.google.com/document/d/13rqtHSlO9hp43ZMsjiGTPwViJBWbmlo3oERaz5lIdD8/edit#heading=h.8qo3tfbu4pb5

Configuration by Code Concept: Configuration by code

Partners weigh in on the topic: http://forum.magnolia-cms.com/forum/thread.html?threadId=dacbff3f-0ce9-4293-b8b2-b5c1843568b7

Readable bootstrap files. See: Concept - Readable config files (Readable bootstrap files)

is the entry point for the whole Config By X theme.

What does it mean

Config By X means that configuration for magnolia can be provided by different means - no longer only by jcr as today. Independently from how it's actually provided these configurations will end up in memory.

 

The Pieces

Config By X basically consists of the model (interfaces + definition classes) as well as the various mechanisms to populate the module (from JCR via Node2Bean, by Code via builders or by file via a new mechanism).

Contents:

Children Display
alltrue

...