Most WordPress developers manage their code snippets by editing them directly in the admin panel. Here's a better way, one that gives you full Git history and lets you deploy changes like any other codebase.
Every WordPress project eventually needs a custom REST endpoint, a data feed for a frontend, a webhook receiver, an integration hook. Loopress Full now lets you ship one as a single PHP file in Git.
Need to pull in a Packagist package on a WordPress site? The usual path is SSH into the server, install Composer, run composer require, and pray. The Loopress plugin does this from the admin panel.
We built a Composer UI for the WordPress admin, then asked wordpress.org's review team if it belonged in the official directory. Guideline 8 says no, dynamically installed executable code is never acceptable there, no matter how it's used. Here's the rule, and the one-codebase, two-edition architecture we shipped instead.
WordPress is powerful. But if you're a developer, working with it can feel like you're fighting the tool instead of building with it. Here's why, and what to do about it.
I'm a frontend developer who cares deeply about DX. Then I had to build a WordPress site, and nothing was the same.
