Let me introduce the two of them for you.

HTML5 Boilerplate:

This is what it sounds like. A basic proof-of-concept foundation for any website what so ever. No need to invent the wheel all over again. It’s important to notice though that it’s not a framework, but a ready made template setup which you then can (usually) scale down safely as well as add on to, to fit your needs.

That’s where the nice CSS Framework grid960 comes in!

The Grid960 is much more of a framework (as far as you can speak of frameworks in CSS). It gives you ready made CSS classes for a grid-splitted layout with a set width (960). Quoting their site;

“All modern monitors support at least 1024 × 768 pixel resolution. 960 is divisible by 2, 3, 4, 5, 6, 8, 10, 12, 15, 16, 20, 24, 30, 32, 40, 48, 60, 64, 80, 96, 120, 160, 192, 240, 320 and 480. This makes it a highly flexible base number to work with.”

There are really nice plugins for Photoshop/AI/Fireworks/Dreamweaver that makes life even easier.

Applying the 960 grid to your boiler template is just a matter of adding the 960.css right after the boilerplates style.css link-tag (Ignore the reset and text css).

Read more about these two at

http://mashable.com/2010/09/02/html5-boilerplate-guide/ – Short intro

http://html5boilerplate.com/- Home of the boilerplate

http://960.gs/ – Home of the CSS grid

..and Some QA for boilertemplate @github

Next up will be chopping it upp all again to fit the CMS or whatever system it needs to fit into (TYPO3 maybe?!)

Updates 24 feb 2011:

Here are some adjustments or additions when working with boilerplate and TYPO3:

Just had to post it. Brings those old memories back to life. Those where the days, right?

Thanks Martin Kool for bringing it all back

It’s really sad that people just can’t see the fundamental philosophy of TYPO3 and the intentions of it’s original inventor Kasper Skårhöj, releasing his work as GPL:d open source software – Inspire people to share!

I few days earlier I stumbled upon a swedish fork/overlay work of TYPO3 called TYPO3 magenta. I got the similar feelings over this one as with that Russian guys fork. Though this is a bit more balancing on the edge. The TYPO3 name is still there but with a suffix. It’s open stated to be built on TYPO3. From the website (freely translated from Swedish using google..):

“TYPO3 Magenta is a web-based system to manage, organize and publish content on websites. TYPO3 Magenta is a further development of the publishing tool TYPO3. TYPO3 is based on open source which means significantly lower costs compared with commercial counterparts. TYPO3 Magenta has developed with the user in focus. The primary user group is Swedish small-and medium-sized enterprises.”

It’s sold in a license form with system, hosting and support.

But as I said, I find this solution better – while not good. I’m guessing it’s mostly about a nifty back end skinn. Refactoring TYPO3 this way is like saying “TYPO3 is good but old school. We make it modern and better with our own version”. And the main issue is still – what would a company loose going 100% TYPO3 and sharing improvements rather then trying to be so special?

I will be honest. We started our business with two CMS solutions. CMS made simple and TYPO3. One simple CMS for the simple sites and one advanced for the larger ones. We promoted them as simple and advanced cms. However during time I realized that both we and the solutions themselves would benefit much more exposing TYPO3 as it is, with it’s huge community and existing brand name rather then trying to make it seem more like our own, and so far it’s just been true. I think that the more credibility and reward the community gets for it’s efforts the better TYPO3 will be.

After all, the community is a vital part of TYPO3 together with it’s open source base. Alongside with that TYPO3 is also a very strong brand and should be promoted and empowered so.

Inspire people to share! – it will get us so much further

So, if your’e a XING user and think you apply to my network pattern (web development, business partners, TYPO3 people, and some more..), please include me in yours!

See my LinkedIn profile as well..

It’s perfect for people like me that just cant get all those object and attribute names to stick in memory.

Now, I’m having a hard time waiting for next alpha or maybe beta so I can test the new front end editing fuzz which at least seems awsome!. Check it out at Jeff Segars blogg.

They die right in front of me leaving me with a broken (long-time-since-last-save) file. Some say it’s about fonts, some say it’s about somethingelse. I saw someone who solved it by buying a new computer..

I contacted Adobe in for the subject, posted an error report and gave them full dumps of my machines current state.. getting the reply to go through a bunch of help yourself links with twenty steps each! Things like that make me grumby.

Anyway.. I’ve tried reinstalling the entire CS4 premium package (uninstall and install taking for ages) without success.. and yeah. one last thing.. Acrobat reader now crashes if I try to open a pdf link within the (a/any) browser. Thanks..

regards,
A grumpy web developer

Not only did we register for the conference but also to become association members for Merea, our company, which feels like the right choice to do as we focus our business more and more around TYPO3 services. It’s a good way of giving back something to the product and community as well as taking further engagement with TYPO3.

So, I hope to meet a lot of friendly faces and get loaded with inspiration and knowledge.

Although the auto update plugin was easy as a breeze to use, it wouldn’t hurt of having some more user friendly error handling when it gets write permission errors and such. They are handled but you get the feeling of being a bit stranded. I had some file writing permission problems.. 

I’m normally doing most of my work with or within the TYPO3 environment, and I must say that the clean and “just working” style of WP is a desirable target for the TYPO3 backend (and others) tool. Really neat.