I started separating the admin from the "theme" by using the wordpress rest api (admin running in a subdomain). While this might seem overkill at first but I find that there's a lot less documentation to read and I can reuse a lot more code from other projects without any changes.
This looks pretty cool. A couple years back, I built a similar starter theme and CLI package for WP dev. Back then CoffeeScript and Grunt were the norm, so it's a bit outdated now. But the CLI actually grew from a scaffold like you have now, to being able to deploy over SSH using Capistrano, database and all, which was really nice.<p>I don't do much WP dev anymore (thankfully moved to using Rails, Go and Node), but when I do I usually use that old project for deployment. I'll be sure to check this out, as the services architecture looks like a nice change of pace. I tried Bedrock/Sage in the past, but it was just too much for me and made some things harder than they should be.<p>Added links to my old projects below in case anybody is curious,<p>[0]: <a href="https://github.com/themejuice/tj" rel="nofollow">https://github.com/themejuice/tj</a> (CLI)
[1]: <a href="https://github.com/themejuice/sprout" rel="nofollow">https://github.com/themejuice/sprout</a> (theme)
Cool. I'll check this out.<p>One thing I really find myself having a hard time working with WordPress themes is that many of them are bloated and require so many plugins. The amount of css/js files that are required to load a page in a premium WordPress theme averages around 30+ files (at least from what I have seen working with WordPress themes).
I built a custom gulpfile that uses composer to manage the updating of WP and plugins along with building and FTP transfer a while back that I've been using for about a year. I should have built a swanky page and open-sourced it then :(. Composer sure makes WP development much easier to integrate with build systems. This is totally the way to go as long as clients prefer using WP to something more full-featured or server intensive. I'll have to check this out when I decide that webpack has some advantage over gulp/rollup. Right now I'm able to get smaller packages and do more easier with gulp, so I'm in no hurry.