Details
-
Improvement
-
Resolution: Duplicate
-
Trivial
-
None
-
2.01
-
None
-
all
Description
While working on developing training material for magnolia we noticed that currently, a developer can only configure templates at the following path: "Config/modules/templating/Templates/myTemplate". However, if there are a couple of projects running in the same instance and each with a set of templates—seems that Templates directory could get out of hand. It seems that we should let magnolians organize their templates more by letting them define their project templates under a new directory- all encapsulated within the main directory "Template". E.g. ".../Templates/myProject/myTemplate".
Furthermore, it would be better that the only convention would be that the template node must be below /Templates. If the template node had a new identification type (e.g. nodetype=template), one could search for all nodetypes=template and present them whenever the author creates a new page (e.g. Template field in "Website").
Marcos