[MGNLSTK-46] templates: create a main template definition bean and use a single main template Created: 10/Oct/08 Updated: 23/Jan/13 Resolved: 19/Dec/08 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | mme_sprint2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Comments |
| Comment by Philipp Bracher [ 28/Oct/08 ] |
|
More or less done. For the content pages (article, news, events) we share the template. For home and section we reuse as far it makes sense (paragraph collections, ..) |
| Comment by Philipp Bracher [ 31/Oct/08 ] |
|
After a deeper analyses it seams to make sense to keep a single main template with an additonal (optional) include for extra header content and a dynamic include for the content of the main div. This helps to understand the unique structure of the html (wrappers, main div, ..) |
| Comment by Philipp Bracher [ 19/Dec/08 ] |
|
Everything bases now on a single main template. |