History: TikiFest Montreal CSS and Themes discussion

• «
• »

            Pascal Luci Gary Patrick Marc Mike Sylvie Rob

had the following ideas


!!Cleanup css tags in templates.


*divs with the attribute "elegant" eg. in tiki-editquiz.php
*align tags in divs
*clear tags.

question are we willing to break existing custom themes that are out there?


needs to be properly documented - advance waring

BIRT: (be it resolved that) __removing all alltributes that are not strict xhtml compliant__ - forcing the removal of most attributes that cause a nuisance. - consensus


compliance tools: use zvon.org as a reference on what is valid or not.

to chack if a given tpl is valid. use the firefox developer tools extentions 


!!themes in mods. 

BIRT: common finding place - all legacy themes in themes.tikiwiki.org themes are shipped into mods.tiki.org - consensus

for these themes to work they have to be consistent with tiki 2


!!lite css as a base for all bundled themes in 3.o

BIRT: the above. consensus
 



!!default templates. 

idea: wiki template shoudl have button row appear at top or bottom or both. 


note: wiki UI and site idenity project in the works for december


method for UI fixes: can we turn on all the features and then design them so that they are not ugly together.


using javascipt to improve usability is desirable but the rule should be not to break tiki - this needs to be evaluated case by case - explain on dev list. 

more and more stringent guidelines are emerging for standards like accessibility.  

!!site identity

site identity allowed certain parts of the theme to be contained in the database. this makes it much easier to upgrade sites with custom themes because the special header is defined by the database. 

!!Basic layout
can we provide for user to pick a basic layout. 

disscussion could we have different tpls for differt. 

iframe
wordpress or kubrick style

discussion favors keeping to a single (if more complicated) tiki.tpl


!!default theme for tikiwiki 3.0
avoid forked tiki

tikiwiki should ship with

darkroom
tikinewt
thenews
simple

default theme should be the theme of the tikiwiki.org website. 
default theme should be sexy and flexible because many peple should not change. 


tiki.tpl should there be just one?

kubrick? rejected for simplicity 
no forking of tpl's period. 


move everthing possible to separate tpls so that only layout exists in tiki.tpl



background image configurable in the admin panel


ability to override themes with DB managed theme - then themes could be managed with profiles. 


a template template

devtools

-a template template - what we think a template should be. 

a wiki page to read showing a ((TemplateBestPractices))

indentation of templates - need to be readable. 

!!Most readable CSS

topstyle css editor shows all the colors. 

included
color manager
Layout
basic html
sitewide classes
feature specific classes

!!CSS Best practices

modify as few templates as possible

use display:none instead of removing code if you want to hide things. 

avoid feature specific classes use decendant selectors instead. 

function specific classes ok.


!!!CSS for tables.

*need a guideline for css for tables
*feature specific CSS in tables needs to be removed.

!!!reducing the number of selectors.

functional selectors for specific features - which are added as new features are available should be either. used for relative placement etc. - should not have design (color formatting size etc.) 

design selectors - 

!Where to find the developer rules (guidelines says marc) about CSS and templates 


please!


see ((110 CSS))