...

• How to handle theme images?
• Would GIT be a fourth option for a loading cascade? Could be -  but people could just use normal git to sync things on the filesystem. So maybe only the filesystem option is necessary.
  
  

To consider -

• maybe things should actually not be loaded to repository. This means you cannot do a clean uninstall.
• Should templates and resources really be loaded to separate locations in separate workspaces? What is the advantage of having these things scattered, instead of together?

Config by File

What if configuration for templates and dialogs could be done in a file instead of in the adminCentral configuration tree?
This comes out of thinking of ways to treat resources and templates more equivelently, ie in a standard way. And then realizing that developers like working with files and have a lot of familiarity with tools and workflows there.

...

1. The format of the bootstrap file is "clean", BUT the bootstrapping behaves the same. Loaded once at install, version updates.
2. The files are loaded every time magnolia starts, and the repository nodes are overwritten.
3. The files are loaded at mag start and used for item definitions, but the repository is not written to or used at all by them.
4. The files are loaded at mag start and used for item definitions, repo is not written to...
   
   1. and adminCentral ConfigTree shows a view of the files.
   2. Edits in adminCentral are saved to the files immediately.
      
      

...

Thought experiment: could the repository know from which file all config comes from? What if whenever a bootstrap is loaded, an additional propertly is written to the root node in the config tree - the filepath of the bootstrap. So from any node you can walk up the tree to determine which bootstrap actually wrote that value. This would kind of be like "source maps" in web resources. What about MVH, would they also write a note to root of every node they change? Or would this eliminate need for MVH?

Editing files vs Editing Configuration - the two seem antagonistic.

Inplace editing of Templates & Resources: Access filesystem

...

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.

...

HTML Modules

This means a few things.

• In AdminCentral, you can create a module. Why? - a place to store your configuration of new apps etc.
• On the filesystem, you can populate a directory - and all contents of that directory are loaded and treated similar to a module - dependencies, etc (what else explicitly?)

...