Ich bin ein Frontend & UI Entwickler aus Bremen. Hier schreibe ich Artikel über Webentwicklung, Design, Software, Workflows und was mich sonst beschäftigt.

Du hast Anmerkungen und Feedback zu meinen Artikeln? Dann schreib mir! Ansonsten folgt mir auf Twitter und abonniert mich auf YouTube.

The Great Divide

css-tricks.com / Direktlink

Two front-end developers are sitting at a bar. They have nothing to talk about.

This is a topic that affects every frontend developer. As a freelance developer, I deal with requests on a weekly basis, mostly from recruiters.
If you sort out all messages that are based on Java, hybris, or other technologies I've never heard of, there are only two types of requests left.

A frontend developer for HTML, CSS (or SCSS, Less, or similar). With UX experience. Some Javascript.
A frontend developer for React / Vue.js / Whatever. Some Redux / Vuex / Whatever. And some UX.

This was a creeping process. At a conference a few years ago I talked to someone who now calls himself a "classic frontend developer". But this implies for me that a "classic" developer is less and less needed, maybe even on a par with a book printer (compared to machine production). And I don't believe that.

Nevertheless, this conversation and the abundance of requests for "modern frontend developers" was one of the things I finally wanted to do more with Javascript frameworks. I even enjoy it. But I wouldn't call this work frontend development anymore, because it includes so much more than UI customization and optimization.

I think we need to move away from the term myself. We should split into UX Engineers and JavaScript Engineers. They are different mindsets. Most people are not amazing at both JavaScript and CSS. Let UX Engineers work closely with UX/Design to create great designs, interactions, prototypes, etc. and let JavaScript Engineers handle all the data parts.

But ... I think I'll save the topic for a blog entry.

Introducing Kirby 3

getkirby.com / Direktlink

After over two years of development and seven years after launching Kirby 1, we are back with our biggest release to date…

Woohoo, finally. Kirby is my CMS of choice and I try to use it for almost every project. The version 3 brings is not only a rewrite, but also some useful new features:

  • a new panel, written in vue.js (woooohoo, again)
  • more panel fields options
  • Drafts & custom publishing workflows
  • a new plugin system (btw, do you already know this page?)
  • and the most important part, at least for me: ... REST API and Headless Browser

    Kirby 3 has a built in REST API. You can comfortably create and edit your content in the Panel, and then consume your content in SPAs, mobile applications or static site generators.

With this release I will probably be able to tick off a long open todo point for the Kirby directory. Use Kirby 3 as backend.