jigsaw VS Cleaver

I decided to choose jigsaw as I am familiar with the technologies it's built with (PHP , Tailwind for styling and Blade as template engine) as it will be easy to customize if needed besides that, it comes with decent amount of features out of the box, I barely did any customization to it, just followed the installation instructions and got started.

JigSaw

Also if anyone knows of any third-party templates for Jigsaw, I can't find any except the default blog and docs that they have in their documentation.

https://github.com/tighten/jigsaw/blob/main/src/Jigsaw.php

I also would argue that the majority of code I see in other languages is equally or worse than the example you gave.

You can write terribly in any language, Laravel included.

We have ~8 Laravel apps and roughly 40-50 Jigsaw projects that we keep up to date like this.

Take a look at Jigsaw from Tighten: https://jigsaw.tighten.co

Now, as for what runs the site. It is a static site, using Jigsaw as the framework. Jigsaw uses Laravel’s blade templating. Since one of my goals this year is to learn Laravel, it was the perfect fit for my site. GitHub is where I've decided to store my repos, and Netlify watches for changes to my main branch and rebuilds my site.

Recently I decided to take on the task of automating my site's build and deployment process through GitHub Actions. I'm using my own static site generator Cleaver to handle that, which requires both Node + PHP to be installed in order to run the asset compilation and build process. Now, GitHub Actions supports both of those runtimes out of the box, but I had just created a perfectly good Docker image for using Cleaver, and instead wanted to use that.