Toolbox Theme: A good start for HTML5 in WordPress

Finally opened this blog with something.

The other day, in Paul Boag’s podcast, Paul interviewed Ian Stanley about WordPress best practices and they mentioned Toolbox, the HTML5 theme they are using as a base for building other HTML5 themes.

I had been struggling with themes a while, but none was clean enough for me, nor easy to modify, but today afternoon I remembered and gave it a try…

This theme is fantastic!

So easy to tweak! just added a few styles, added our webfont, and voilá! 30 minutes later I had a published decent HTML5 Worpress Blog.

Still tons to do, but now there is no going back, it’s so HTML5 semantically correct, a bit too much for my taste. I’m still not convinced about the multi H1  in the document outline, so I’m tweaking a little more, for better backwards compatibility.

I guess one could see this as a Boiletplate for HTML5 themes.

Toolbox Theme: Parte HTML5 en WordPress con el pie derecho.

Finalmente he abierto este blog con algo.
El otro día, escuchando el podcast de Paul Boag, Paul entrevistó a  Ian Stanley sobre buenas prácticas para WordPress. Mencionaron varias cosas, pero entre ellas me llamó la atención un theme llamado Toolbox, que Ian y su equipo han estado usando como base para hacer Themes HTML5, me imagino que lo usan como un Boilerplate, para plantillas de WordPress.

Había tenido problemas con este blog desde hace tiempo, las plantillas no me acomodaban. Muy pesadas y sucias algunas y otras tan complicadas de modificar, pero hoy en la tarde me he acordado de Toolbox…

Este theme es filete!

Tan simple de instalar y editar, como no tiene fotos y es semánticamente correcto, me bastó agregar algunas líneas de CSS, nuestra webfont y listón dePaloDeMaderaDeÁrbol! en 30 minutos tenía un blog HTML5 decente funcionado.

Aún faltan toneladas de cosas por afinar, pero ya no hay vuelta atrás, es tan correctamente HTML5. Quizá un poco mucho para mi gusto. Todavía no me convence esto de tener múltiples H1 en el delineado del documento, así que estoy ajustando el html para que sea compatible con algoritmos de delineado más viejos (backwards compatible).

Rant on Flash, HTML5 and Uncle Steve

What I don’t get is this visceral hatred towards flash, I know it allows bad design, but so does jQuery, CSS3 and dear Photoshop. jQuery using more battery than flash for the same task.

Don’t get me wrong, I think JQuery, MooTools and others similar are one of the best things to happen to the internet, but, just as flash, it’s not the panacea.

People seem to forget that the main attribute to flash is not animation, it’s the ease for making things work across platforms. Plugin architecture is far from ideal, but clearly it has worked far better than asking Software Companies to stick to a spec. 3 specs if you want to do what flash does.

If Steve Jobs claims sloppy coding on behalf of Adobe, but one can say the same about how Apple works with hardware.

Flash has huge improvement to do efficiency wise, still needs ways to handle crashing and resource utilisation. Flash Player 10.1 addresses this quite decently. Still I was hoping that with SC5 they would work on something better.

This is far from over, and I think this could lead to mayor mayor changes like the settlement of HTML5 as a real, stable, adopted spec. Or huge improvement on the flash platform and the fulfilment of the Open Screen Project (which, as a developer, am a bit ambivalent on).

The huge problem I have with JavaScript is performance (even on Chrome), compared with ActionScript 3, which is absurdly fast considering it is an interpreted language.

That would be the rant I had been choking on for a few weeks.

Let the wrath of the Open Source righteous rain on me.
I might soon elaborate on this a bit…