jigsaw VS Packagist

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.

What will we do next time? Actually, the whole package is ready, and all that's left is to publish it on Packagist.

publishing our work on https://packagist.org/

The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."

Composer is (still) the defacto standard package manager, with the Packagist repo being the standard place to find and install libraries.

Sorta—it looks like they were most enforced by convention until May 2015, when they finally become enforced [0]. Still, that's a good one that I hadn't thought of, and they at least had the convention in place.

[0] https://github.com/composer/packagist/issues/163#issuecommen...

Scanning your image for vulnerabilities is a critical step before you deploy it to production. You can use Snyk to scan your PHP Docker image and identify and resolve vulnerabilities. The Snyk Vulnerability Database includes records for all popular operating systems and dependencies, including PHP packages published to Packagist.

No. The only linked commercial thing I know - is Nova admin panel interface lib. But you don't have to use it. (Filament or Encore are free and suitable). Modules are free ( packagist.org and gthub.com ) and you should handle them with standard composer package tool. But you need to code. It is not WordPress like CMS

Once you understand the underlying principles of a concept, you're free to find a library via packagist.org to use.

For strings I use Stringy (https://github.com/danielstjules/Stringy) for arrays I built my own Collection library, but pretty sure there are plenty in packagist (https://packagist.org/)

I guess I tried downloading a old version. and have to download a newer version of apiclient I found on https://packagist.org/packages/google/apiclient with monolog/monolog: ^2.9||^3.0. I'll try that in a second, I am away from computer now.