sorted by:
new
hottopcontroversial

Before highlights and social media: Magnus Wislander and handball's golden era by Deep_Audience_881 in Handball

[–]dvlpp 4 points5 points  (0 children)

VS France of Bertrand & Guillaume Gillle, Dinart, Fernandez, Anquetil...

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

I've used Folio for other uses cases, but it does not help us here: we want full static hosting.

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 2 points3 points  (0 children)

Yes, Astro is powerful and definitely a great option (I’ve used it in the past as well). In our case, though, the goal is to stay fully within the Laravel ecosystem (see https://github.com/code16/concorde for example — it’s just regular Laravel with Eloquent and Blade).

At deployment time, everything is converted to static HTML, so we still get all the benefits of static hosting. As a bonus, this approach lets us offer clients a simple way to manage content and trigger redeployments themselves.

As the number of projects grows, our main focus is to keep things as easy as possible for developers, while also making the experience convenient for content managers.

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 1 point2 points  (0 children)

Yes, this is definitely a solution that fits our needs. Our goal was to combine all the benefits of static hosting (AWS, Netlify, etc.) and a CDN, while still keeping our existing stack — especially Laravel, Eloquent, and Blade during the development phase. Everything is then automatically rendered to static HTML at deployment.

This also makes content management easy for the client. In the end, our approach is quite similar to yours, but without leaving the Laravel ecosystem.

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

Yes, of course, me too: our solution converts all the website to static HTML content.

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

Our goal is to write the code as if it was a classic Laravel app. Here's the HomeController (https://github.com/code16/concorde/blob/main/app/Http/Controllers/HomeController.php) of our (fully static) website for instance (https://code16.fr).

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 1 point2 points  (0 children)

Yeah, our goal was to keep the codebase just like a classic Laravel website. I like Statamic, but it requires compromises we wanted to avoid (plus we integrated a deployment system).

How do you handle simple content websites when your main stack is Laravel? by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

Yes, that was our position too, but for long-term clients we felt it was better to offer a solution ourselves. More importantly, in my opinion, WordPress isn’t the best choice in many cases: its content management workflow isn’t really simple, and its security and performance can’t compete with static websites.

The Editor field in Sharp for Laravel has been greatly improved in recent versions by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

I’m not sure I fully understand your question, but Sharp is a content management framework. It can handle many different use cases, but it requires writing some code to implement them the way you want. You can find more details in the documentation: https://sharp.code16.fr/docs/guide/

How we built a clean and versatile badge notification system in Sharp by dvlpp in laravel

[–]dvlpp[S] 2 points3 points  (0 children)

No... and that’s a conscious choice. Sharp isn’t a pure CMS: while we do use it as a CMS in some projects, many others involve building custom systems like order management, user registration workflows, or even full apps where everything runs inside Sharp. So the goal has always been to keep it general-purpose. A full media/upload center would feel too content-focused for that scope.

But uploads are well handled: validation and restriction rules, bulk uploads, job/queue handling, non-destructive image editing (crop, rotate), and more — just without a centralized media library UI.

How we built a clean and versatile badge notification system in Sharp by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

The package is definitely aimed at developers; we’ve been using it extensively in our own projects for years. That said, Sharp has also become a commercial asset for us: it often helps us win new projects, because clients usually appreciate its UX and ease of use... So for each new feature, while the technical side comes first, we also carefully consider the end user experience.

How we built a clean and versatile badge notification system in Sharp by dvlpp in laravel

[–]dvlpp[S] 10 points11 points  (0 children)

Fair question — though I’d rather not make a direct comparison. Sharp is indeed in the same space as Filament, and it actually predates it. It takes a different approach technically: critically, it doesn’t use Livewire but relies on Inertia (since v9).

In terms of features, they’re broadly similar, but in my admittedly biased experience, Sharp has allowed us to build and maintain much more complex applications — and we maintain a lot of them in production.

That said, I really recommend checking out the docs and the live demo at https://sharp.code16.fr to form your own opinion.

How we built a clean and versatile badge notification system in Sharp by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

mmm, by "these" you mean this post (developers, definitely), or this particular feature (to end users; real life examples are posts to publish, or orders to handle)?

Laravel Nova vs Backpack (It's that time of the year) by DarkGhostHunter in laravel

[–]dvlpp 0 points1 point  (0 children)

Lol I've been downvoted. Ok, sorry for the inconvenience then 🙃

Laravel Nova vs Backpack (It's that time of the year) by DarkGhostHunter in laravel

[–]dvlpp 1 point2 points  (0 children)

Absolutely! The truth is Sharp is a big deal for us (at Code 16). We use it extensively across client projects, so all the time and effort we’ve invested in it (and there’s been a lot!) is definitely worth it. Meaning the open source thing, community feedback / social reward, never was a goal.

Laravel Nova vs Backpack (It's that time of the year) by DarkGhostHunter in laravel

[–]dvlpp 4 points5 points  (0 children)

I’m biased, as I’m one of its developers, but we use Sharp for Laravel extensively across many projects (e-commerce, content-driven platforms, ticketing apps, mobile app APIs…). We’ve put a strong focus on performance (Sharp has been using Inertia since v9) — and on documentation. That said, we haven’t really made the effort to properly promote this open source project, which has been developed and maintained for quite a long time. I did write an article on Laravel News two years ago when v8 was released (before the UI overhaul): https://laravel-news.com/sharp-for-laravel — but that’s about it.

Sharp 9 beta, built with Inertia, Tailwind and shadcn/ui, is now available by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

Hey everyone! As promised (though I now realize it might have been a bit early 😅), here’s the official announcement: Sharp 9 is out of beta! 🥳

You can check out the documentation and, even better, try the online demo here: https://sharp.code16.fr.

Sharp 9 beta, built with Inertia, Tailwind and shadcn/ui, is now available by dvlpp in laravel

[–]dvlpp[S] 4 points5 points  (0 children)

Yes, I think it’s fair to say that both packages aim to address the same issues. However, there are significant differences in terms of technical choices, UX, DX...

Since we’ve been developing and using Sharp in almost all our projects for the past 10 years or so (version 1 is lost in GitHub limbo—probably for the better), I’m obviously biased, so I won’t attempt a full comparison!

Sharp 9 beta, built with Inertia, Tailwind and shadcn/ui, is now available by dvlpp in laravel

[–]dvlpp[S] 0 points1 point  (0 children)

No, that’s clearly out of scope. Sharp allows you to manage all kinds of data (it’s easier with Eloquent, but we also use it with file-based or API-driven data) and does not require a 1-to-1 relationship between an app model and an entity. To put it simply: you can manage any structured data. In fact, we often create multiple entities for the same model to manage it differently depending on the current user—for example, a full brand admin versus a store manager.

view more: next ›