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

Some concepts Concepts which will be implemented in 5.4 have become children of page Concepts 5.4Here 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 filesystemConfig 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.

...

http://wiki.magnolia-cms.com/download/attachments/42270723/stk-remarks-vpro.pdf

Template & Resource loading cascade & Filesystem loading

Templates & Resources (and any other file assets) should be treated equivalently where possible.

Current problems

...

Proposal

In order to stay flexible and support different use cases - system should implement a "loading cascade": loading things in a specified way from a specified series of locations
By default, Templates/Resources should be loaded in the following order. Items loaded later override the previous ones. The order goes from least flexible to most flexible.

1. Modules (classpath).
2. Directory on the filesystem.
3. Repository that have "override" box checked.
   
   1. A master configuration item causes all items from repository to override.

(Alternatively, perhaps the mechanism only loads templates/resources that are not yet defined, instead of overwriting as defined above, in which case the default order would be reversed.) 

Filesystem loading

• System should watch all files in configured directory and when changed
  
  • reload them in the system
  • add them to the repository, reload them to the repository

Questions:

...

To consider -

...

Inplace editing of Templates & Resources: Access filesystem

...

• 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)

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

...

Proposals for Consideration: (How to find file)

• Filename is written as a property to the root node of the configuration it represents. So on change, it can walk down the tree till it finds the filename (or flag).
• Unlike bootstraps, ConfigFiles always start at a specific level. There is a separate file for each app, each dialog, and the basic "config" node for a module. As this is set - its easy for the system to generate the filepath of the file and check if it exists.
• All files are scanned to find matching file.

Questions

If a user makes a ConfigTree change to a node that is not created by ConfigByFile, does system create a file for this manual change?

If a user makes a ConfigTree change to a node that is created by ConfigByFile, but by another module - it's not correct that this change be written to the file of another module. If anything it should just be written to the "project module". As the project module has super dependencies, its always loaded last and so its ConfigFiles would be applied last, mimicking the manual change.

Javafree Template

What would the file structure be for a component template stored in a directory. 
templateName.xml could be the template definition that ties everything together.

...

...