You may gasp in horror at the thought of extra markup — I’ll be in the pub Friday evening by 6pm.

A pragmatic approach to responsive grids by @dbushell

I received an email from 1&1 last thursday telling me the website at www.example.com is infected. Indeed, the website shows a warning page when accessed with Google Chrome, however, it redirects to www.example.org. This is the infected website. So I told 1&1 that this is a false positive because this is just a redirect and the domain the redirect points to is not under my control. I also asked them to check their systems so they don’t bother me with these false positives in the future.

The reaction was exactly what you expect from 1&1: They told me example.com (which was not infected) is under my control and I should fix this ASAP. Well, you can’t fix what’s not broken and so I send them a screenshot with the following:

matthias:/htdocs/example.com/httpdocs # ls -al
total 8
drwxr-x---  2 examplecom   psaserv   22 2011-03-01 10:22 .
drwxr-xr-x 13 root         root    4096 2011-04-10 21:48 ..
-rw-r--r--  1 root         root      66 2011-03-01 10:22 .htaccess
matthias:/htdocs/example.com/httpdocs # cat .htaccess
RewriteEngine On

RewriteRule .* http://www.example.org/ [L,R=301]
matthias:/htdocs/example.com/httpdocs #

So I have done exactly nothing but 1&1 congrats me for solving this issue. They don’t get the point. And because of that I will have to life with these false positives in the future.

This blog is now responsive. As I hadn’t had the time to do it on my own I used the Tatami-Theme by Elma Studio. There is a lot of good stuff in this template and you can learn a lot from just using it. Of course there are some things I don’t like, too. But I guess that’s the price you have to pay when you use something off-the-shelf.

I also want to use this relaunch to get a consistent line regarding my blogs. So this blog will focus on work-related things and will be in english most of the time. Thanks to the Tatami-Theme I can now also post quotes, links and videos in a more tumblelog-style. Blogpotato will become (or remain) the geek stuff blog in german and I will continue to blog about becoming a vegan on Ist mir egal, ich ess das jetzt einfach (also in german, the URL translates to „I don’t care, I just eat this now”). And, if this wouldn’t be enough: I bought a flat lately which is currently under construction. Thoughts on this subject (in german) will be published on K12.

Dan Cederholm on what’s really important in web design.

Trent Walton on, well, where to start in responsive webdesign.

As I’m currently planning on doing more with SASS this tutorial by Martin Wolf comes in handy.

Another one by Brad Frost. And yes, I’m guilty of boring people with the more technical aspects of performance optimization.

Brad Frost pretty much nails it: The Post-PSD Era. Because it’s http:// and not psd:// (this also might be a quote from Brad, I’m not sure so let me know if it’s yours).

What it does is accessing your webpage, clicking links, filling out forms and checking on the results (URL, Status Codes, etc.). I just implemented it for checking all of our stores checkout processes once a day.
Setting up is straigt forward and easy (as long as you have a check left in your Pingdom account). The Check editor offers context sensitive suggestions on actions and validations and has instant feedback on how long it took to perform the action and wether it was successful or not.

So with the Transaction Monitor annyoing repetitive task can be automated and thanks to that performed even more often as when executed manually.

For some inexplicable reason however there is an artificial limit on the number of steps you can add to a check which is currently 25 and limits the usefulness unnecessarily.