I've just released a minor update to my Baseblog Kirby Theme. It includes some fixes, some general code improvements and a few new features.

Just check out the changelog for more information!

GithubShowcase

Template engines are made to make the life of frontend developers easier, to separate logic and layout and to provide handy shortcuts for common tasks. Those are all reasonable arguments, but they all don't mean that you have to invent another language for it. Kirby in fact has a template engine – a simple one, which is based on PHP. PHP can be the perfect tool to write templates, you just have to do it the “right“ way.

Maybe some of you are a bit scared of dealing with PHP like I was, before I started building websites with Kirby. This great article by Bastian shows what Kirby is all about. In case you're looking for a new lightweight and flexible CMS, you really should not be hesitating and give it a try because with Kirby it's way less complicated to write templates in plain PHP as you might think.

I can only speak for myself, but Kirby took away my kind of skepticism regarding PHP.

Some months ago I asked myself why the heck it's not possible to print background-colors/images in Chrome and Safari. I still don't know if this is some kind of a bug or a feature. Maybe you know the answer...

I've built a first version of a project directory based on the awesomeness of Kirby a few weeks ago. And after using it for a while I'm gonna release it now, so you can check it out as well.

When it comes to web development with Kirby on Windows you might use XAMPP as your local server environment. At the beginning of the year I wrote a [german] post about installing Kirby on XAMPP which many of you might still find while searching for some kind of tutorial. In the meanwhile Kirby has changed in some parts which are crucial in this case to uncomplicate those installations.

After the new design and the move from Wordpress to Kirby it's time to post a few lines about the further development of Sashtown going on these days.

So call it responsive or adaptive, the critical idea is to maintain a One Web approach. That is, to use open web standards like HTML, CSS and JavaScript, and to deliver an amazing experience to your users through the same URLs.

Inspired by the upcoming iPad Mini James Sherrett wrote a damn good read about how to deal with the adaptive approach when it comes to building cross-device capable websites. He emphasizes that the so called responsive stuff is just a pretty small part of the whole user experience we should seek for.

Mit Webplatform.org ging heute eine Art allumfassendes und Community-gesteuertes Nachschlagewerk, welches als dokumentative Sammelstelle für Informationen rund um Webtechnologien dienen soll, an den Start.

The maincontent element represents the main content section of the body of a document or application. The main content section consists of content that is directly related to or expands upon the central topic of a document or central functionality of an application.

Steve Faulkner brachte gestern einen Entwurf zur Erweiterung der HTML5 Spezifikation ein. Er schlägt ein neues Element namens <maincontent> vor, welches - wie die Bezeichnung bereits suggeriert - den hauptsächlichen und einmaligen Inhalt eines Dokuments auszeichnet. Dadurch sollen Semantik und Zugänglichkeit von Websites in Kombination mit dem WAI-ARIA Attribut role="main" gefördert werden. Ein sinniger Vorschlag, auch wenn mir ein griffigeres <main> besser gefallen würde.

Im Zuge einer angestrebten Tarifänderung meines T-Mobile-Vertrags und den damit verbundenen Gegebenheiten habe ich den Herrschaften bei der Telekom einige Zeilen des Unmuts zukommen lassen, die ich Euch nicht vorenthalten möchte.