One year after Joomla v4.0.0 might be an excellent time to write honest opinions about that release. Mainly on the bad things.

Site or App? SPA or MPA? React, Vue, Svelte, Solid, Lit, μhtml or another framework/library? Use the platform or use a trendy framework? Let's start with plain HTML and figure out if we can reach the other end of the spectrum in a progressively enhancing way...

For ages Joomla didn't have any meaningful way to handle user created overrides for templates. Did you changed any file from the template? Possibly your changes will be reverted in the next update. Things have change, now there are child templates and they promise to solve those cases and maybe a few more.

Creating live examples from code snippets in a site, particularly a documentation site, is extremely helpful for users, as they get to play with the code. Eleventy (rightfully) didn't have such functionality out of the box but don't despair...

According to urbandictionary.com, the term is described as software that comes piggy-backed on other software installations. Bloatware usually includes toolbars desktop widgets or external unrelated applications. Most piggy-backing bloatware can perform a mundane task that is generally non-essential to everyday computer use.

Joomla 3.9 introduced a new feature for content privacy which is a great addition to the tools provided out of the box but, after 4 patches and countless mentions for it, still has a flaw. A major one...

Monolithic applications, like PHP CMS', usually need a way to synchronise the state of the client [browser] with their own, but there are cases that a stateless application will work fine. Let's explore how we can achieve a cookieless Joomla instance

Joomla 4.0 is painstakingly crafted by a bunch of people. One of the main areas of improvement was to simplify the convoluted User Experience. So how things are evolving? What’s the plan there?