This document relates to the "Lower the Entry Barrier" initiative, codenamed "Ramp".

Some concepts which will be implemented in 5.4 have become children of page Concepts 5.4

Here I will go into more detail about some of the concepts. These will probably be broken into individual documents.

Concepts to cover:

Template & Resource Loading Cascade
Inplace editing of Templates & Resources: Access filesystem
Config By File: Configuration & Bootstrap improvements
- Work with config more like templates & resources.
- JCR Document View or JSON. Autoloading. Autoexporting
- Maybe it works like code in that it creates a dynamic configuration every time - not a permanent change to the configuration tree.
Better Javascript handling.
ConfigTree improvements. Extends insight. Template Extender tool.
Enable frontend developers to create apps & fields with templates.

References

Inplace editing of Templates & Resources: Access filesystem

What if nothing was stored in repository?: Not templates or resources?

Templates and resources do not get stored in repository.
- Admincentral apps load the files from filesystem for display.
- inplace editing - edits the files directly. (In exploded War)

That does not work for JARS, the files cannot be written to.

If writes to the configTree were automatically written back to the ConfigFile - that would solve problem of loosing changes made in adminCentral.

But how would the system know to which file to write?

And how would it know when to write given the likely situation that some configuration is defined by File, but some is loaded from Bootstraps?