WordPlate: WordPress on Composer with sensible defaults
1–10 of 105 posts
Re: WordPlate: WordPress on Composer with sensible defaults
#2Congrats on releasing, we built something similar (WP/composer) for our stack, you can see the details here: https://docs.altis-dxp.com/getting-started/
Re: WordPlate: WordPress on Composer with sensible defaults
#3What advantages does WordPlate have over Bedrock[1], some of whose packages WordPlate also uses?
Re: WordPlate: WordPress on Composer with sensible defaults
#4I always wonder, at what point is it easier to just ditch Wordpress completely and instead spend the time to add an admin theme that looks & behaves like it for familiarity of users, and maybe add whatever magic functions your favorite framework might be missing.
This isn't a critique, I use WP intensively, and we heavily modify and extend it as well, but the familiarity of the team (in dev, seo and content) is pretty much the only selling point, because we shut down most extra features (feeds, rpc, json-rpc, emojis, gutenberg, comments etc etc etc), use a complex varnish-setup, do image optimization etc outside of it and most plugins aren't really good, so we roll out something custom instead. Getting rid of it it isn't an option for us because we're so committed and have built so much custom stuff around it, but with a green field, I'm not sure.
Re: WordPlate: WordPress on Composer with sensible defaults
#5I always wonder, at what point is it easier to just ditch Wordpress completely and instead spend the time to add an admin theme that looks & behaves like it for familiarity of users, and maybe add whatever magic functions your favorite framework might be missing. This isn't a critique, I use WP intensively, and we heavily modify and extend it as well, but the familiarity of the team (in dev, seo and content) is prett…
I think you answered your own question, the familiarity for users (seo & content) which is "end-to-end no-code" is massive (especially once extended with user-facing plugins). And you're not even speaking about making the move to Gutenberg yet. Just too much value there.
Re: WordPlate: WordPress on Composer with sensible defaults
#6Just reading this again gives me a backflash of the horrors of working with WordPress. If you haven’t seen the source, you don’t know just how god-awful the code is - and it just won’t die, because of all the ecosystem traction it has.
Even the PHP developers have chosen to ignore WordPress in language evolution considerations, as the WordPress community refuses to do accept kind of progress for their project - they still use the unsafe, outdated mysql-API without parametrised queries, for example.
Whatever you do in 2023—if you can avoid it, don’t use WordPress as a CMS.
Re: WordPlate: WordPress on Composer with sensible defaults
#7I always wonder, at what point is it easier to just ditch Wordpress completely and instead spend the time to add an admin theme that looks & behaves like it for familiarity of users, and maybe add whatever magic functions your favorite framework might be missing. This isn't a critique, I use WP intensively, and we heavily modify and extend it as well, but the familiarity of the team (in dev, seo and content) is prett…
I think you answered your own question, the familiarity for users (seo & content) which is "end-to-end no-code" is massive (especially once extended with user-facing plugins). And you're not even speaking about making the move to Gutenberg yet. Just too much value there.
Yeah, certainly, but that's what I meant to address by making your framework's backend look & feel like WP and adding e.g. shortcodes to it and having a media library that works the same way (but doesn't suffer from WP's clunky bolted-on attachment).
Gutenberg isn't a thing for the folks I work with, nobody there likes freedom (freedom only leads to errors!), everything is form-based (ACF is slow but it works, and here, too, it's not users setting up the fields, it's developers) with a few shortcodes to pull in special elements.
I'm not complaining, I like building tools and solving problems and using WP allows for plenty of both, but in hindsight WP is slowing us down, I believe. Of course, it's hard to predict the scale of things when you start, so having something you can quickly iterate with is useful.
Re: WordPlate: WordPress on Composer with sensible defaults
#8Just reading this again gives me a backflash of the horrors of working with WordPress. If you haven’t seen the source, you don’t know just how god-awful the code is - and it just won’t die, because of all the ecosystem traction it has. Even the PHP developers have chosen to ignore WordPress in language evolution considerations, as the WordPress community refuses to do accept kind of progress for their project - they…
WordPress uses the PHP-mysqli extension. The PHP-mysql extension is unused since WordPress 3.9, quite some years ago. You might mean PHP-pdo is advised. Can you explain why it is better in this regard?
Also $wpdb->prepare() uses parametrised values. Not everywhere in WordPress core is it being used. Most plugins use it for direct queries (not that common), but I don't know if the plugin team refuses plugins when they are not using it.
Re: WordPlate: WordPress on Composer with sensible defaults
#9Just reading this again gives me a backflash of the horrors of working with WordPress. If you haven’t seen the source, you don’t know just how god-awful the code is - and it just won’t die, because of all the ecosystem traction it has. Even the PHP developers have chosen to ignore WordPress in language evolution considerations, as the WordPress community refuses to do accept kind of progress for their project - they…
There's much more to WordPress than the ecosystem. If we just think of it as a legacy tool that is only limping along because of the plugins, we will forever be perplexed that it continues to exist.
WordPress is the FLOSS alternative to Wix et al. It is the only practical software that enables people to create and self-host an online presence without having to type a single line of code, and without being beholden to a large centralized platform.
No, a static site generator that requires knowledge of Markdown and a few lines of bash doesn't count. A CMS that requires you to hire a professional to even get started doesn't count, either. It might seem strange to developers like us, but there are lots of people out there who are simply allergic to code. They can use PowerPoint and maybe even Photoshop, but show them a blank terminal and they'll just freeze. WordPress, on the other hand, can be navigated with a bunch of point-and-click, drag-and-drop, buy this and add that and change the options a bit. Just like PowerPoint, it barely works, but it works.
Very few people in our startup bubble seem to care about these "I want a website, but no code please" people, and when we do we often treat them with contempt. How hard can it be to copy and execute a few commands, after all? But apparently that market is large enough to attract a sustainable ecosystem of plugin and theme sellers. WordPress has this market completely cornered. It won't magically disappear just because it's built in crappy code. Understand the users, on the other hand, build a good alternative, and that billion-dollar market might become yours. :)
Re: WordPlate: WordPress on Composer with sensible defaults
#10Just reading this again gives me a backflash of the horrors of working with WordPress. If you haven’t seen the source, you don’t know just how god-awful the code is - and it just won’t die, because of all the ecosystem traction it has. Even the PHP developers have chosen to ignore WordPress in language evolution considerations, as the WordPress community refuses to do accept kind of progress for their project - they…
Why would you change a successful product just because the "language evolves"?
PHP is so successful precisely because it lets all the legacy code live.
To the contrary, with each PHP iteration, "bad code" is executed faster with fewer energy utilized.