If you have any interest in checking it out, getting involved, or just want an excuse to learn a little about how Laravel works from a WordPress developer's perspective, let me know.

OK, if you've gotten this far in the thread, here's the buried headline: what started as a learning project has kind of turned into something I might be interested in building out further. It's far from prod ready, but I'm close to what I would consider "very early alpha" state.

The procedural code in WordPress is a bit easier to grok by looking directly at the source code. A particular method in #Laravel might be several layers deep in an abstract class, traits, etc. But I almost never find myself needing to look at the source, the docs are THAT good.

The documentation is detailed AND extensive. I almost never get "stuck". I learn a new trick or technique almost every day just by following accounts like
x.com/@tnylea, x.com/@PovilasKorop, x.com/@mmartin_joo, @calebporzio.bsky.social , @aaronfrancis.com, and others.

I have to say, I'm blown away by how well it's going. #Laravel has everything you might want. All the stuff we take for granted that WordPress (if you think of it as a framework) does, but honestly, way more, and better in pretty much every way.

Coming from deep within the WordPress world, I figured why not try to build a CMS like WordPress? Worst case scenario, it's too hard to do, and maybe I'll still learn something from trying.

“I can’t see how to do a good job, and I don’t want to do a bad one.”

I feel seen.

WordPress has become an anachronism on the web, running on old architecture with old programming ideas as if the web in 2024 is what it was in 2012. As a result, WP skills are becoming less and less transferable.

"Webmasters" is a fantastic name. I love it!