So while I have been spending allot of time making design and skins, I think I finally closing in on some neat ways to write the code so it’s understandable even to people not so use to write CSS.
And I have some ideas on how to make a pretty nice skin that I think could serve as an standard and flexible one.
The first thing would be to set some standard “class” and “div id´s” so that the main part of a skin is easy to recognize and also editable true the css file.
and so on....
To take the edit part a step forward I think we also should use explaining and matching texts markups in both the css and tpl file.
/* start header */
the css code here
/* end header */
<!-- start header -->
the html code here
<!-- end header -->
So what do you think about this, would it be worth the effort?
Also have some more ideas on providing 3.parts of the header, index and footer tpls. Like 2.column, 3.column, and a 4 column one so that the designers will have more standards to start with.
Could also make a pure and fast css one without images and one that uses images ,, well well have plenty of ideas about this tell me what you think and we could start from there..