wordplate VS wprig

Found some discussion here, but tbh it's a little light for me not to think that NIH syndrome doesn't come into it?

https://github.com/vinkla/wordplate/issues/234

My stack is currently Wordplate as the base, with Lumberjack as the starting point for my theme. I then use ACF Pro to define Gutenberg blocks in PHP.

Some starter themes for devs support Tailwind CSS, besides Roots/Sage those are: wd_s, wpemerge, wordplate (they use an abstraction on top of webpack called Laravel Mix, there are official Tailwind docs for it).

Wordplate, seems to go with the flow and adds just a thin layer on top of standard WP.

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.