Everything’s shiny and new around here! And it’s not just a visual refresh, the technology here is all new. I’ve switched from my beloved Textpattern CMS to WordPress. I didn’t expect that to happen, but it allows me to create content for this English and the German website at yatil.de from the same backend. Also the Website is indiewebified thanks to the tremendous work of Matthias Pfefferle. He created the Sempress theme and various nifty WordPress plugins. With Textpattern I would have developed most functionality myself and I don’t think that I would have found the time to do it.

The transition was painlessful. For example I had to go through each and every post and remove excerpts that were created automatically. Also there were no featured images carried over from Textpattern, so I had to assign them manually as well. That has been quite a bit of work for articles reaching back to 2004. I tried to catch everything, but there may be some rough edges around here.

Main objective of the transition was to post stuff more efficiently, the wide-spread integration and tools available for WordPress really help there. Please keep the webmentions coming, so I can be sure everything works.

I’m going to continue to publish here on my own website, journal, blog, or whatever you want to call it. It’s still possible that I might lose everything but I’d rather take the responsibility for that, rather than placing my trust in ”the cloud” someone else’s server. I’m owning my own words.

Really good article on why we should host our content ourselves and why it is so hard to understand for younger people. This is a must-read!

In this fantastic video from the Webstock ’13 conference, Mike Monteiro shows that designers need to take responsibility for their actions. There are many things I touched on with my article Be Proud to be a Web Developer from almost a year ago, and it’s worth watching. From the description:

You are directly responsible for what you put into the world. Yet every day designers all over the world work on projects without giving any thought or consideration to the impact that work has on the world around them. This needs to change.

[… M]ethodologies [like OOCSS and BEM] attempt to apply the principles of Object-Oriented Programming to CSS. Notwithstanding the conceptual incompatibilities between a declarative style language and object-oriented software design principles, these methodologies introduce subtle problems which may not be immediately obvious to less-experienced developers. Most disconcertingly, these methodologies have seen widespread adoption thanks to prominent bloggers evangelising their usage as ‘best practice’.

Ben Darlow on Cargo Cult CSS

While OOCSS classes may be understood by programmers and HTML novices, they put the design into HTML, it is the <font>-Element all over again. Little gain for complex HTML. True object oriented CSS has the objects in the CSS through SASS, rather than in HTML.

I don’t say “Don’t use classes!” but try to describe the content. A table with the class products can easily be made striped and narrow in SCSS:

%table-striped {
    td:nth-child(odd) { background-color: #eee;}
%table-narrow {
    td { padding: 2px 3px; }
.products {
    @extend %table-striped;
    @extend %table-narrow;

Don’t want the product tables striped: Change one line in your SCSS. With OOCSS you’d have to go through every HTML template and remove the class “table-striped”. If narrow tables aren’t in the style guide after a redesign, remove one line (inside %table-narrow) and boom, all your tables aren’t narrow anymore. Same if the narrow style changes. It’s one change in one file (probably an included _table-styles.scss) and not searching through many template and HTML snippet files to change it.

Your HTML should be clean, your CSS can be messy.