I'm messing about with Kube as a way of converting existing designs to responsive. So far so easy... until I get to the bottom of my example home page and I have 3 columns that need to have a border between them that goes the full height. Take a look at http://tauranga.nzpif.org.nz/ In Kube you create the columns as "blocks" and use unordered lists. Looks easy. Some the css is a bit messy because I'm overriding the old CSS. Any ideas on what I need to add to get this working? I've looked at a few other bare bones "frameworks" and none seem to handle this out of the box.
Can't say I've heard of "Kube", but from what I'm seeing it appears to be non-semantic crap that's abusing lists for elements that already have perfectly good section markers semantically (in the form of headings). It's the same garbage as the HTML 5 asshattery of the SECTION or NAV elements... which mated to the typical CSS framework garbage of presentational class use means I'd be talking about pitching that junk in the trash BEFORE even talking all the accessibility failings I'm seeing -- like the fixed metric fonts, inaccessible color contrasts, lack of at the very least elastic layout, nonsensical heading orders, lists around non 'bullet point' (as in a grammatical bullet point, not as in the presentational "has a bullet before it") elements, and to be frank layout concepts (like equal height columns) that may not be 'viable for web deployment' on what you SHOULD be aiming for -- a semi-fluid elastic responsive layout. Even just simple ****, like whoever told you it's ok to declare font-size:10px; on CONTENT... well, in desperate need of a good swift kick in the groin. Clearing DIV like it's still 2001? STRONG around things that shouldn't be receiving "More emphasis"? H3 with no H2 much less H1 for them to be subsections of? Non-breaking spaces and vertical-breaks doing padding and border's job? Four stylesheet embeds with NO MEDIA TYPES much less static CSS inlined in the markup? Jquery for nothing (though to be fair I say that about EVERY project that uses that fat bloated idiotic scripting train wreck), images for text content... Laundry list of how not to build a website -- as evident by the 9.5k of markup and 57k of CSS to deliver 1.38k of plaintext and by all accounts ZERO actual content images... 1.5x to 2x the markup needed and five times the CSS... with 13 files doing 8 or less file's job. "none seem to handle this out of the box" -- go with your instincts on that, it's telling you something. Idiotic crap like CSS frameworks is ALWAYS the road to failure, and I've NEVER seen a site built with that type of garbage that was worth a flying purple fish. Just another example of why I advocate building a logical semantic HTML document before you even THINK about what it's going to look like with the CSS.
Don't you just love inherited code, no time budgeted for fixing it but still needing to get stuff done Some of that "good stuff" was actually done by a designer!
Apply a class to each of the footer elements (#homenews, #homeevents, #homecontact). Class = .footer-full { min-height:100%!important; }
Oh, and if you're "overriding a lot of css" as you said, that too should be telling you all you need to know about that framework.
The framework css is fine, it's the layering of auckland's template, blended with waikato's, chopping and mixing to become a new one without the client wanting to spend $ on getting it "just so"