To start with making our wiki up to date (in both regions: content and installation) we should take a moment to think about future and not the past. I would prefer to have conversation about what we would love to see, then bother about how we gonna get there. There for I would like to suggest few high level regions and reach mutual agreement on, that we all would support.
According to many web designers most of websites should be able to achieve good readability and modern look with usage of 5 colors only. Mostly 4 colors in same range and one as eye-catcher. I propose first 8 colors, more for the range allocations than anything else. Pallets below are for demonstrations purposes only.
| dn-TK1 | dn-TK2 | dn-TK3 | dn-TK4 | dn-TK5 | dn-TK6 | dn-TK7 | dn-TK8 |
| dn-RT1 | dn-RT2 | dn-RT3 | dn-RT4 | dn-RT5 | dn-RT6 | dn-RT7 | dn-RT8 |
| dn-MR1 | dn-MR2 | dn-MR3 | dn-MR4 | dn-MR5 | dn-MR6 | dn-MR7 | dn-MR8 |
But to make our wiki more attractive using 4+1 should do the trick. Something like this:
| dn-RT1 | dn-RT2 | dn-RT3 | dn-RT4 | dn-RT5 | dn-RT6 | dn-RT7 | dn-TK3 |
| dn-RT1 | dn-RT2 | dn-RT3 | dn-RT4 | dn-RT5 | dn-RT6 | dn-RT7 | dn-MR3 |
In my opinion, to make it even more flexible/dynamic, numbers should be replaced by variables like {{color}}, {{background-color}} which will contain specific number.
No HTML tables, all in CSS. CSS is faster and 'easier' for browsers to interpret. It is more flexible.
We all know what template is. But do we know when is a template a good template? Friendly for contributors and as functional as it gets? Example below demonstrates my idea of templating in stages. Templet call should be as straight forward as possible. This can be best seen in button 4. How to keep templates easy to use? I suggest using templates containing subtemplates.
Further in text there will be better examples of this construct.
Here some of my interpretations of staged templating:
No HTML buttons, all in CSS.