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:

...

• 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.pdftoc

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?

...