I’m experimenting with describing all my CSS and JavaScript behaviors in XML. Currently working on allowing the optional nesting of CSS selectors which results in rules generated with normalised versions.

for example..

<selector css="pre">
    <style>
        font-size: 1.1em;
        background: #f0f0f0;
        -moz-border-radius: 10px;
        padding: 1em;
    </style>
    <selector css="span">
        <style>
            font-weight: bold;
        </style>
    </selector>
</selector>

I’m hoping this will make my life a little easier.

Need a way to specify the kind of selection being made. child, descendant etc. This is very very important for usability and for generating something that create a CSS that will render without boiling the ocean.

Read a post by Simon Willison today about taming the CSS monster, the comments pointed to some interesting resources, I added my 2c. I think what I am building in WireWrap will go part of the way towards solving the problem for me and improve the system that I am building as a whole – but as a general solution what I think we really need is good support in the IDE for CSS introspection and management.

All the rest is self discipline, good planning and knowing how CSS actually works.