[MAGNOLIA-277] request to arbitrary structure config Created: 03/Feb/05 Updated: 14/Jul/05 Resolved: 14/Jul/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Bert Schulzki | Assignee: | Sameer Charles |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
For dialogs you can create a hierarchy to organize your dialogs below config:/modules/templating/dialogs. This is not possible for Templates (below config:/modules/templating/Templates) and Paragraphs (/modules/templating/Paragraphs), they currently must be maintained all in the same folder. This makes maintainence of templates nasty if you have a larger amount of templates and paragraphs. Therefore magnolia should be extend to support a hierarchy for template and paragraph definitions, similiar to the dialog definitions. Bert Schulzki |
| Comments |
| Comment by Sameer Charles [ 03/May/05 ] |
|
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 -------------------------------------------------------------- ts a very good comment, now we have a possibility to search on nodetypes I think it makes perfectly sence to define node types for config data. Sameer |
| Comment by Philipp Bracher [ 14/Jul/05 ] |
|
New more 2.1 related task: 474 |