Where to begin! Where to begin…

Lets start with a good measure of success, one that I think most engineers could
agree with: a from-scratch rebuil...

Artsy's resource offers insights, tutorials, and resources for artists, art enthusiasts, and collectors. Readers can learn about art history, contemporary art trends, and collecting tips. With articles, interviews, and artist profiles, Artsy provides  guidance and expertise for navigating the art world and discovering new artworks.

Artsy.net

Artsy shares their experience with Next.js over the past two years, including the success of rebuilding their internal tools app, the excitement around Next 13 and React Server Components, and the challenges and limitations they encountered during the migration process.

Two years of Next.js at Artsy: A Retrospective

<p>I wouldn’t touch NextJS too way to much dependencies.  You can probably build something quick and simple using HTMX, AlpineJS and Hono</p>


<p>The App router is such a mixed bag. On one hand theres a lot of great improvements, RSC, better file structure, etc, but on the other, theres a lot of compromise with the DX, needing to separate server/client components/ weird cache issues, hard to escape nested layouts, etc. I recommend looking at Qwik/QwikCity, better code splitting, better DX, no need to split out client components, ability to escape layout files (ie use a specific named layout file where needed), etc,</p>
