Server and client finally clicked
The tree mental model in the first lesson cleared up months of confusion about use client. Everything after built on it nicely.
Browse
Server Components, Server Actions, PostgreSQL with Drizzle, authentication, caching and deployment in one real project
Created by Amara Okafor
Next.js with the App Router lets you write the server and the client of a web app in one React codebase. That is powerful, and also confusing at first: which code runs where, what gets cached, and when does a component need "use client"? This course answers those questions by building one complete app.
We build Shelf, a reading list app where users sign in, save books, write short notes and share public lists. It has real persistence in PostgreSQL, authentication, forms that work before JavaScript loads, image optimisation and SEO friendly public pages.
Every concept is introduced when the app needs it. You will see the network panel often, because watching what the server actually sends is the fastest way to understand the App Router.
You should be comfortable with React components, props, state and hooks, and know basic TypeScript. You do not need prior Next.js experience. If you have used the older Pages Router, there is a short lesson mapping old concepts to new ones.
Full stack JavaScript developer teaching React, Next.js and Node through real projects
I build web applications for small product teams, mostly with React, Next.js, Node.js and PostgreSQL. Most of my week goes into the unglamorous parts: data fetching, forms, auth, error states and deployments that do not break on a Friday.
My courses follow one project from an empty folder to a deployed app. I explain why a pattern exists before I show it, and I leave my mistakes in when they teach something useful.
Outside client work I mentor junior developers and review a lot of pull requests, which is where most of my lesson ideas come from.
The tree mental model in the first lesson cleared up months of confusion about use client. Everything after built on it nicely.
I liked that Amara showed why checking the session in a layout is not enough. We had exactly that bug in production.
Seeing a form submit before hydration was a small revelation. The validation pattern with useActionState is now standard on my team.
The caching lessons are the best I have seen, but it is a complex topic and I needed to rewatch them twice.
The course is good but moves quickly if your React is rusty. I paused to review hooks first and then it was fine.
The data layer setup is clean and typed end to end. I copied the structure into my own side project.
Covering both a managed platform and self hosting was useful. A Docker compose file in the repo would have been nice.