Our great sponsors
-
TYPO3
The TYPO3 Core - Enterprise Content Management System. Synchronized mirror of https://review.typo3.org/q/project:Packages/TYPO3.CMS
-
gutenberg
The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
wp_template_opinionated
an opinionated classic WordPress theme template, modern code style, pure postCSS, standalone, with minimal blocks support, forked from wp_template
-
-
-
elementor
The most advanced frontend drag & drop page builder. Create high-end, pixel perfect websites at record speeds. Any theme, any page, any design.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
I doubt that WordPress is in danger. Its multiverse / flexibility and ease of use compared to real content management systems like Typo3, NEOS or Drupal, and the ability to just install it and control your content on your own webserver, try that with Wix, WebFlow, SquareSpace, Shopify and all those "serverless" software as a service servers. Hopefully, the core team will either get their block editor right some day (WordPress 7.0?) or make it completely optional. That would still be better than a fork, but I'd wished they had improved security, performance and internationalization instead of releasing the new editing features in an unstable beta state.
WordPress 6.2 “Dolphy”, the first major release in 2023, includes more than 900 enhancements and bug fixes. But WordPress/gutenberg still had 4842 open and 18128 closed issues at the time of writing, including 1051 open issues labeled as bugs.
A side product of my research and development, wp_template_opinionated is my own WordPress starter theme boilerplate. It includes several aspects of what I found to be a useful project setup close enough to popular development trends and official best practice.
I hope that you have found some useful advice in this article series about WordPress development. Hopefully, this will be my last post about WordPress. I will be looking into other site generators and frameworks like NEOS and Symfony, and continue my ongoing JAMstack and MERN side projects in 2023, and also continue to explore and blog about new and upcoming HTML, Vanilla JS and CSS features.
The template repository has been forked from wp_cli_docker to help us build a classic (child) theme from scratch (without exporting from the block editor), that follows the official WordPress coding standards. We can still support and provide custom blocks in our theme.
For the sake of simplicity, my example setup uses a single-file plugin and puts all styles directly into a single style.css file without using further theme.css or theme.json files, which we might want to use depending on the requirements for customizability. Likewise, SASS / SCSS support can be added if it makes life easier for the developer(s) involved. But as we already use PostCSS to control autoprefixing and cssnano minification, we can also use it to support the latest and even upcoming CSS sytax like native CSS nesting.
WordPress is celebrating its 20th anniversary and it still powers millions of websites all over the world, so we can say that's an open-source software success story. The "WordPress multiverse" has been fragmented for a long time, due to a multitude of possible combinations of plugins and page builders like Elementor? But efforts to unify mainstream development and obsolete page builders doing full-site editing using the Gutenberg block editor has caused controversy. No-code enthusiasts are happy about the new features, while developers get frustrated about breaking changes and unfinished development rolled out and promoted as the new default as part of the "from blogs to blocks" campaign.
For the sake of simplicity, my example setup uses a single-file plugin and puts all styles directly into a single style.css file without using further theme.css or theme.json files, which we might want to use depending on the requirements for customizability. Likewise, SASS / SCSS support can be added if it makes life easier for the developer(s) involved. But as we already use PostCSS to control autoprefixing and cssnano minification, we can also use it to support the latest and even upcoming CSS sytax like native CSS nesting.