CMB2 VS WordPress-Plugin-Boilerplate

So far in this current project, I added CMB2 as a composer dependency, and that's done just enough to take away the headache of adding custom metaboxes and input fields to different pages. I feel like maybe if I just get myself the most basic toolkit to handle these common tasks, and a boilerplate to start me off with some structure, I may be able to wrap my mind around the way WP expects things to be added and registered the more I work with it.

You might also check out CMB2, which is a bit more efficient query-wise with repeater fields than ACF Pro.

I just started on a new plugin, and I used this boilerplate as my jumping-off point. So far, it seems to abstract away from wordpress just a little less than something like the Underpin framework I linked to in the original post does, so I feel like it's helping me get a bit of a feel for how WP handles things, while also adding some much-needed structure and doing things like helping separate the dashboard side from the frontend side. As for the REST API side, where would you turn to that? Is that just when you want to expose bits of the site to external services, or would you use it to allow internal components to communicate with one another or something like that?

https://pippinsplugins.com/learn/. I learned quite a bit from Pippin. I use the WordPress Plugin Boilerplate when I create custom plugins (https://wppb.io/). If you go that route, you'll end up learning OOP PHP in the process.

The WordPress Plugin Boilerplate is a nice template for starting your next plugin. It's certainly not the only way to do things, but you can learn a lot by going through it.

Take a look at the plugin boilerplate repo to get an idea of how a good plugin (with more than just basic functionality) might be set up. Way down at the bottom of plugin-name.php, it calls run_plugin_name(), which then calls other things and other things and other things, etc.