It's time to talk about the portfolio itself

I'm going to put some illustrations of the site's configuration section, since it's only visible to me :)

Everything is managed by Composer.

For the backend, we have Laravel, in detail: Eloquent for the ORM, middleware for route permissions and to throttle certain sensitive requests, policies for CRUD permissions, Laravel Breeze for authentication, Laravel-Lang for multilingual support

For the frontend, I use Blade, Laravel's view engine, coupled with Tailwind for CSS, and a few Node libraries for JavaScript (for example, the filter component in the news section uses tomselect, a small JavaScript library). Scripts are compiled with Vite

Everything is managed from a backoffice (including this article), from which I can declare categories, programming languages, give them colors, then put it all in my blog articles or in projects afterwards (image carousel included)

To compile my past and future projects, and also feed a "Blog" section in which I show a bit of what I do in my free time

I followed Grafikart's tutorial on Laravel 10 (although the site is on Laravel 12), so it was a first step with Laravel and Tailwind. Initially I also wanted to integrate React components to make everything prettier, but ultimately it was too complicated to learn such an important stack all at once, so my next project will normally be a full frontend project in React, with API fetches, then when I'm comfortable, I think I'll do a Laravel + React project using Inertia (React integrated into Laravel)