[T3 stack] Warm-up — Environment Setup — CRUD Example — Deployment

5. Update in progress

Adding features beyond the example, in progress: adding the delete function that exists in note but was missing from topic... and partway through, getting distracted by other things... ㅜ

4. A one-line review

As I always feel — every framework is becoming Spring-ish. I don't know what Spring is like these days ;), but the terminology is fading from memory now. I should drop by that neighborhood again sometime... 

3. Deployment 

https://notetaker-4mzz.vercel.app/

https://github.com/normalstory/notetaker

2. Notes: environment setup and development 

: Typescript, Next.js, postgresql, Supabase, TRPC, DaisyUI, Vercel

https://www.notion.so/thinknormal/f30e346e12ac446e91289d2023caadfd

1. Warming up

After a long break, when I came back to look at React and Next.js, so much has changed. Of course, it has changed for the better. The so-called DX — a recent buzzword? in this field — developer experience is improving. (Well, vanilla js and css are also under continuous update, after all.) Backing everything up before starting would take forever, so for now I plan to follow along and catch up using the most comprehensive and representative recent example. Before that, as a warm-up, I'll first do a thorough read of the major posts.

About. Next.js

1) The most intuitively important part, the one that needs understanding first, seems to be the routing and rendering architecture part that organizes and outputs information (the screen). For reference, from v13.4 onward the APP Dir has been adopted (it can also be used in parallel with the PAGE Dir method) and is structured in a directory-based manner. Nested routing configuration is also possible — many blogs mention this. Personally, I think the most important concept is that screen composition is no longer managed at the page level but instead is broken down into components (partials), with rendering managed at that level. Against that backdrop, the layout pattern that was used in the previous Page Dir method is being applied again, and the strategic direction has shifted from "how to render the entire app efficiently" to "how flexibly can we choose or release per route." (  "State management in Next.js" article and the Next.js official docs)

*Related official docs: https://nextjs.org/docs/app/building-your-application/upgrading/app-router-migration