Recently I wrote about the ‘expiring’ editor Atom. Now I’ve stumbled upon another dead horse in my stable: YAML CSS. That has nothing to do with YAML ain’t Markup Language. It’s a modular CSS framework for truly responsive websites. For years, it served me faithfully, first in Typo3, then on WordPress. And now?
In the GitHub repository of Yaml-Css , there are still two open pull requests from 2013/2014 and 11 issues from 2013 to 2017, but zero contributions since 2014. Since 2010, Xing and Linked-In consistently show its main author, Dirk Jesse, as ‘Editor-in-Chief’ of the trade magazine “Bautechnik”. Additionally, he has stopped publishing activities under webkrauts in 2014.
No, I’m not doing YAML-CSS wrong if I say it’s dead. Anyway, I couldn’t recommend the wife to build her new web presence on it.
But now I have to become active myself: fodina.de has to be rebuilt. Especially since — as the woman never tired of pointing out — it looked so ‘old-fashioned’. And since I no longer wanted to be resistant to advice, there was only one thing to do: Get rid of it. Set up a new concept, using
So I myself have to become active again: fodina.de has to be updated too. Especially because — as the wife never tired of pointing out — it looked so ‘old-fashioned’. And because I didn’t want to be ‘advice-resistant’ anymore, I had only one option: Get rid of it! Look for
- a future-proof HTML/CSS framework as a basis
- that is demonstrably also open-source software,
- minimizes my daily effort
- invites readers
- and is leaner in terms of content.
And how does this …
… support our migration to bootScore? Well, if a web designer must abandon her current WordPress theme, she needs a replacement. A free ‘off-the-shelf’ theme, she probably wants to personalize. First a bit cosmetically, then in terms of the gray value of her pages, multilingualism and internal reference techniques and linking. Finally, she perhaps enables special footers, a secondary menu or a copyright notice before checking the SEO features of the selected theme. This is a way that this post supports too.