JointsWP VS wprig

I'm sure there's a bunch more, but I've personally used JointsWP and love it, as well as my employer for previous themes. There's a SASS option to download that works great out of the box.

I love JointsWP for starting from scratch - it uses Foundation 6. https://jointswp.com/

Joints WP - Bit unsure about this one. The theme CSS file is empty but the functions enqueue a foundation css file that is thousands of lines long.

JeremyEnglert/JointsWP - A blank WordPress theme built with Foundation 5, giving you all the power and flexibility you need to build complex, mobile friendly websites without having to start from scratch.

What the other commenter said about Roots is the way I've done it in the past, but honestly it was such a ballache. Instead I just have the templates in a github repo, with a db backup running fairly often. I use https://wprig.io/ for my templates, and just commit the template before building and putting it on stg or prod.

Haven’t used it yet but this looks pretty interesting https://wprig.io

Of course you can declare a use statement at the top like, use WP_Query. See example here: https://github.com/wprig/wprig/blob/f4e1189a4540b14d3d74bda9a3f28136df0a4fcd/inc/Image_Sizes/Component.php#L12

Also http://wprig.io (see V2 in the nav menu)

wprig, complete dev package with a modern workflow.

WP Rig includes a Gulp build process out of the box. It too had weird dependency errors last I looked, but it looks like there's a new version out now. It uses a PostCSS flow instead of Sass, so YMMV.

Not every project will require (or care) about commit squashing. That said, there are no projects that require not squashing commits. To be on the safe side just give ’em a squash.