[MTE-7] Provide rudimentary page/area templates to be used when no demo-projects are installed Created: 30/Jan/15 Updated: 04/May/15 Resolved: 30/Jan/15 |
|
| Status: | Closed |
| Project: | Magnolia Templating Essentials |
| Component/s: | ftl-templates, models |
| Affects Version/s: | None |
| Fix Version/s: | 0.5 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Extract STK functionality |
| Description |
|
Most page templates rely on the current STK / Demo Project. If modules want to provide default page templates (e.g. with auto-generated, default content elements), there should be a simple, standard page templates (main.ftl) which renders the content without having to install any demo. To prevent duplication of such templates/code, we suggest to put them into the MTE models module. Developers can easily override the templateScript with their custom template but have a good starting point without having to rely on any demo. |