[MGNLSTK-361] themes: create centralized themes configuration and make it easy to switch themes Created: 01/Jun/09 Updated: 23/Jan/13 Resolved: 01/Jun/09 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
By introducing the themes (theme jar, specific module version handler, bootstrapping) we have just done the first step. Since the theme as such is not physically maintained but just be setting the css to load in the site configuration, this has been reason for confusion. As it is our goal to have multiple themes we must make the next step and bundle the theme configuration and follow the concept of having themes more consequently. |