4 ms·
> Don’t make the mistake of believing the default settings of WP come from any kind of informed wisdom instead of historical accident. I don't, thanks. To rep
by throw46365 2y ago
> Don’t make the mistake of believing the default settings of WP come from any kind of informed wisdom instead of historical accident.
I don't, thanks.
To repeat myself, I just say it's better not to assume they are wrong.
Almost every bit of bad WP development out there comes from people who work against the flow of what WP is doing, whether because they don't understand or do understand and feel they know better.
They may, in fact, know better, but it's almost always wasted energy that leads to future unmaintainability when a WP site is handed to a new stakeholder for example.
The WP sites I've had to maintain where someone has subverted the templates, or tried to superimpose some MVC scheme, or whatever, have always been the worst ones.
There are good, official tools to manage most of the idiosyncrasies of WP (WP-CLI, for example) without just arbitrarily moving stuff around. Learning them helps.
- chuckadams 2y ago> To repeat myself, I just say it's better not to assume they are wrong. Normally advice I would heed, but my long experience with WP's codebase has flipped that assumption. It's WP's default layout that's the unmaintainable mess, much like every other legacy PHP project that doesn't use composer. Bedrock isn't "arbitrarily moving stuff around": it's a mature product maintained by people who know what they're doing, which frankly puts them a tier above most of Automattic. I use wp-cli alongside bedrock, they work nicely together.