[MGNLSTK-407] Make template hierarchy configurable (as opposed to pluggable) Created: 30/Jun/09 Updated: 23/Jan/13 Resolved: 30/Dec/11 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | concept |
| Affects Version/s: | 1.1 |
| Fix Version/s: | 1.5 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Christian Ringele |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
Explanation:
I want to rise here a discussion, if this should be dynamically configurable over the site configuration or not:
One use case is for example:
Wouldn't it make sense, to have this definable directly in the site configuration? |
| Comments |
| Comment by Christian Ringele [ 01/Jul/09 ] |
|
To be more precise: One 'pro' argument: |
| Comment by Philipp Bärfuss [ 28/Jul/09 ] |
|
I don't understand. The template availability is configured under /site/templates/availability Are we talking about a more fine grained configuration? Then the title of the issue would be misleading. |
| Comment by Christian Ringele [ 12/Aug/09 ] |
|
@PH: Yes, the title was missleading. |
| Comment by Christian Ringele [ 12/Aug/09 ] |
|
Second use case: STK is built up the way, that you can configue your site and edit the templates&resources within STK. NO need of an IDE for that. |
| Comment by Christian Ringele [ 14/Sep/09 ] |
|
I talked on the conference with Aperto about this use case. |
| Comment by Christian Ringele [ 30/Dec/11 ] |
|
Closed to our experience, that:
|