What would it take for WordPress to reach a next big milestone of accounting for 51% of the web? Here's a hypothetical long-term roadmap as a thought experiment, targeting enterprise clients as the next big audience to tackle.
In a previous instalment, we identified the Config file as being a promising tool to map data reusable code to project-specific code. In this third article, we'll examine what our Settings page example looks like if we do indeed make use of such a Config file.
WordPress Philosophy seems to indicate that all design decisions are ultimately run by the user base to get a "democratic" voting of what changes to implement or reject. However, the reality is far from that. Is WordPress missing a "voting" system?
Recount of my impressions of being a first-time volunteer and first-time speaker at a WordCamp, two personal premieres I was able to experience at WordCamp Frankfurt 2016.
While the first part of this series identified the need to separate business-specific logic from reusable code, we haven't yet discussed how to best achieve this. Let's try to think it through...
OOP lures you with the promise of making code reusable, but OOP syntax alone does not make your code reusable. Let's find out why that is, and how to really write reusable code.
Including an autoloader within WordPress is not an all-or-nothing endeavour. With a few simple changes, we can have a fully functional autoloader being loaded with WordPress, and we can start refactoring the existing Core code to gradually load more and more classes (and even functions) through the autoloader.
Ryan McCue, Senior Engineer at Human Made and WordPress Core Developer, has posted a series of tweets regarding the fact that WordPress is far from an ideal platform for developers, which has spawned a lot of discussion.
As a long-form response to this, here’s a list of changes I would like to see in WordPress, and how I would try to address backward compatibility (BC) concerns. I don’t pretend to know that this is the absolute best way to tackle the problem, this is purely my own biased opinion, and how I would try to fix the issues if I were in charge.
I am currently on a quest to find the perfect setup for my WordPress projects (who isn’t, right?). I do think that a large part of what makes or breaks complex software projects is dependency management. And there are dependencies at every level of your projects, be they languages, libraries, servers, stakeholders, whatever. When someone pays you to attack a project (outside of hobbyism), he generally pays you to fulfil a business goal. And it’s your task to keep the things in check upon which this business goal “depends” on.
The problems you’ll deal with when trying to manage these dependencies are not new to your project; they have been the same problems for many moons. And many smart people before you have found solutions to these, which can be found somewhere on a spectrum from “satisfying” to “perfect”.
You’ll probably agree that it is best to learn from other people’s mistakes and reuse their solutions, instead of being stubborn and insisting on making these same mistakes yourself (wasting a lot of time & money in the process).