On Wed, Jun 17, 2009 at 3:18 PM, Dan Cheail <[email protected]> wrote:
> > > It's not SASS that makes / prevents these from being semantic. It's > > the fact that by using a "Css framework" you're effectively putting > > style information into your markup. > > You realise that DIV and SPAN (and the id and class attributes) aren't > semantically significant, and are there simply to provide general- > purpose structure? For example... > > <div class="column half left"> > <h1>Important Heading.</h1> > <p class="introduction">Lorem ipsum dolor sit amet, consectetur > adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore > magna aliqua.</p> > > <blockquote> > Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris > nisi ut aliquip ex ea commodo consequat. > </blockquote> > > <p>Duis aute irure dolor in reprehenderit in voluptate velit esse > cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat > cupidatat non proident, sunt in culpa qui officia deserunt mollit anim > id est laborum.</p> > > </div> > > ... is still semantically rich, correct HTML. > > > -- > Dan Cheail > Chief Geek, Codeape. > phone: 0402 114 697 > web: http://codeape.net > >From the 960 front page: <div class="container_12"> <div class="grid_7 prefix_1"> <div class="grid_2 alpha"> ... </div> <div class="grid_3"> ... </div> <div class="grid_2 omega"> ... </div> </div> <div class="grid_3 suffix_1"> ... </div> </div> > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
