Building a reading list web app as a side project, using node, preact, and tailwind CSS, you might ask yourself, what is my purpose?
This must have been done a thousand times before.
I finally took some time for proper research (and some lazy trial and error based on tutorials and example code) to set up a proper full-stack application for three main reasons:
We don’t have to be frequent flyers to leave an ecological footprint.
Carbon dioxide emissions pollute the air where it aggravates climate change, and the same also happens when we are using the internet. Video streaming and conferencing, gaming, and mining of cryptocurrencies only represent the tip of the iceberg.
Badly written websites contribute to the destruction of the environment as well, by consuming unnecessary amounts of energy for servers, transmission infrastructure, and for display and update on the client-side, that is, in your browser on your desktop computer or on your smartphone.
In this article, I will tell you why I started plugin and theme development, and show you some examples of my work.
First of all, a plugin API is a great achievement. Back in the day, we used to modify existing software by overwriting source code, which made upgrades hard or impossible.
Some popular web software that has come a long way since the early millennial internet boom defined plugin interfaces, so that software developers could extend and modify existing software while still, at least in theory, being able to upgrade the core software nevertheless. Both WordPress and Software opened…
Recently, I asked myself if my WordPress blog was ready for PHP 8 already?
Why did I care? PHP 7 ran much faster than PHP 5 did, and the upgrade to PHP 8 also promises to benefit web speed and thus, better web performance, which is, in turn, helpful for search engine ranking (even more so with the Core Web Vitals update in May 2021).
It is amazing to see how PHP has evolved, both its core performance and syntax, as well as the community standards (PSR) that provided de-facto standards that make it much easier to learn one framework…
Google’s “Core Web Vitals”, Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS) can help us to measure and optimize web page speed, usability, and search engine visibility. Thanks to Addy Osmani and Houssein Djirdeh from Google and to everybody else for their explanations. This article is based on my original article on dev.to.
I have been writing web content for decades, never being independent as I depend on the world wide web infrastructure anyway. But I kept blogging, posting, and discussing here and there, and when I finally thought I might contribute something to that ominous medium platform some marketing colleagues keep talking about, I did some research…
I did some research about medium and came up that many web developers have already left medium for dev.to, so this is where I will probably put some content soon. Besides complaints about the article editors (which reminds me of Gutenberg blocks without the features)…