Feature #4963
Build a proper skinning API
| Status: | Closed | Start date: | 2009-10-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Interface | |||
| Target version: | - | |||
| Tags: | ||||
| Votes: | 0 |
Description
As part of creating a new, clean skin for 4.4, I think we should aim at having a proper skinning API. We should try not to focus only the design, as this is a subjective matter and will never please everyone (see discussion about new login screen in 4.3).
So that proper skinning can happen, a clear separation should be made between the parts that do the scaffolding and the design proper.
Scaffolding will rely on:
- HTML templates
- structural CSS
Design will rely on:
- "Clothing" CSS
- Icons
There should be clearly defined ways of changing those parts: where to place files, naming conventions, method calls to use, etc.
This is a very short and rough analysis, but I think it should be a guiding principle for the revamping of the TYPO3 4.x skin.
History
Updated by Fabien Udriot almost 2 years ago
- Status changed from New to Closed
I am closing this issue since the "new" skin goes exactly in that direction. Re-open the issue if you think something is missing.