wprig VS air-light

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.

I did the same a year ago, and ended up with air-light theme https://airwptheme.com/

With this naked theme u can define all blocks you want! https://airwptheme.com/

Air Light is great. https://github.com/digitoimistodude/air-light

So, can you elaborate on which devices it is not accessible and how? Just quickly tested out with OnePlus 8T and seems to work. Sounds like a bug have emerged for some device then. Please tell me more about the problem or even better, open an issue and we'll look into it! https://github.com/digitoimistodude/air-light/issues

Air light theme https://github.com/digitoimistodude/air-light

Regarding theme development: If you want to develop a 'classic' WordPress theme, I would base it on a Starter theme such as Underscores (underscores.me), Dude Air-Light (https://github.com/digitoimistodude/air-light ) or Sage (https://roots.io/sage/ ), which helps prevent common mistakes.