Why Nova?


I am not updating these docs because my focus is on my new PHP Serverless Project.

My LaSalle Software's purpose was always a mixture of learning, marketing, and a basis for my own projects. It has, and is, fulfilling these purposes magnificently!

As always, contact me with your questions.


Why did I decide to use Laravel's Nova package for my administration back-end?

There are almost a dozen admin packages for Laravel. Some of them are free, some are commercial. Each come with their own set of pros and cons.

I built my own admin back-end for LaSalle Software version one. I did not like what was out there - there was no Nova - so I took an HTML admin template and adapted it for Laravel. Then wrote all the back-end processing.

I was going to build my own back-end admin for version two, then along came Nova

No relation to this song:

Nova is authored by the Laravel Project specifically for the Laravel Framework. I dove in.

The core thing I want from Nova: it should work hand-in-glove with the Laravel Framework.

Who better than the Laravel Project to make an admin package that works fluently with the Laravel Framework? Policies. Guards. And of course, database and eloquent.

On top of this, if the Laravel Framework changes, then Laravel's Nova changes with it. Furthermore, Nova added features to support Laravel's Vapor -- see https://nova.laravel.com/releases/3.1.0.