Facilitate editing of all YAML settings in the site.yaml config file

[mikegcox]

Currently editing the site.yaml file is limited to default data. It would be good to be able to edit all the YAML in that file as it is a good place to store site settings that a website content administrator would need to make changes to periodically.

[rhukster]

Thanks mike...

[rhukster]

Things that need to happen here:

1. user/blueprints/ merged with system/blueprints. Currently user/blueprints are picked up but completley override he ones from system. So you must copy all blueprints from system to user or it breaks things.

2. Supporting @extends would be good, currently this sends things into an infinite loop.

I'm going to ask matias about these things which are really needed before we can implement this functionality.

[rhukster]

Also we might be able to provide the 'extra' fields in a textarea rather than in hidden json encoded fields as they are now.

[mahagr]

I've been thinking something like this for both blueprints and twig; to be able to say extends parent. We do need similar functionality also in Gantry 5 as I really hate copying the whole files because of the base file cannot be seen.

[mahagr]

Fix for 1) is in: getgrav/grav@4a59b8a

[mahagr]

Fix for 2) is in: getgrav/grav@c4cd355

Just note that it allows only single level of inheritance -- I will need to think up a way to generalize the function.

[rhukster]

Very cool! Closing...