| Thread Previous • Date Previous • Date Next • Thread Next |
On 12/11/11 01:20, Francis J. Lacoste wrote:
On 11-11-11 07:48 AM, Deryck Hodge wrote:On Fri, Nov 11, 2011 at 12:25 AM, Huw Wilkins<huw.wilkins@xxxxxxxxxxxxx> wrote:Hi everyone, Here is my proposal for how we should structure our CSS. I'm sure I have missed things or structured things poorly so for my sanity it would be good to get some feedback. Once that's done I plan to add this to the wiki with some examples. I will probably find a bunch of missing info once I actually start doing the work, but this is a start.Hi, Huw. I quite like the proposed rules and structure. +1 from me. Just a question for clarification... we have lots of little bits of css living in "assets" directory in each individual yui widget directory. Will we maintain this? Is that part of what you meant by "components" in your guide? Or are you seeing this css moved out to a central css directory and organized by widget?I have a similar question. The overall proposed organisation if we were a pure-content site. But I'd like to have clarifications on how this CSS is going to interact with YUI. Are we dropping the YUI CSS stylesheets? What about all the CSS class auto-generated by YUI widgets? How is this going to be maintained and how are the YUI conventions are going to fit into ours?
My hunch for YUI widgets is that we keep them as they are. That means maintaining the same directories and other conventions (we may also not want to use LESS for these files too, depending on how difficult that makes things).
We can defer to our standards in other ways, but I suspect sticking to the YUI conventions is going to be easiest. If I'm wrong about that let me know.
We still have many things outside of YUI widgets that we would call a component. Notification banners, bug tables, portlets.
This documentation has been moved to https://dev.launchpad.net/UI/CSSRestructure and I will keep adding to it there.
| Thread Previous • Date Previous • Date Next • Thread Next |
