StackShadeStackShade Library
All courses
Web Development

Next.js Full Stack

From React Server Components to server actions, caching, auth and deployment — learn Next.js the way production teams use it, building real features instead of todo demos.

Intermediate
7 weeks
7 modules · 35 lessons
STACKSHADE / COURSE
Web Development

Next.js Full Stack

LEARNER OUTCOMES

What you should be able to do

  • Choose SSG/SSR/ISR/streaming deliberately for every route
  • Fetch, cache and revalidate data without waterfall bugs
  • Implement mutations, auth and file uploads with server actions
  • Deploy with caching, edge and observability done right
TOPIC FORMAT

Every topic has two modes

Read — deep article with diagrams, artifacts and retrieval.

Present — focused deck with notes, pointer, timer and fullscreen.

Review — spaced review queue with due dates and recall ratings.

Focus — Pomodoro sessions, daily goals and a persistent scratchpad.

Loading progress…

Read → predict → inspect → retrieve. Your progress stays on this device.

0%
Loading study desk…
STUDY LOOP

Designed around learning, not scrolling

Each topic now has the full loop: article, visual explanation, artifact, retrieval and a recordable presentation.

Retrieval

Recall before revealing. The attempt is part of the learning action.

Spacing

Return at increasing intervals instead of rereading everything immediately.

Generation

Predict the next state or answer before seeing the worked version.

Dual coding

Pair compact prose with diagrams, traces, tables and motion.

Feynman

Teach the idea back in plain language to expose missing links.

Interleaving

Contrast nearby problem types so recognition becomes more useful.

CURRICULUM

Pick a topic

React mental models: UI = f(state), hooks rules
Video14 min
ReadDeck
Server vs Client Components — the real boundary
Video16 min
ReadDeck
Interactive: classify 10 components as server or client
Interactive12 min
ReadDeck
Composition patterns: passing server into client
Video12 min
ReadDeck
Refactor a client-heavy page into RSC
Project40 min
ReadDeck
FEYNMAN PROMPT

Teach the server/client component split as a restaurant menu (printed once) vs the interactive table tablet.

ACTIVE RECALL
Why fetch data in Server Components when possible?

No client waterfalls, direct DB access, zero JS shipped for static parts — and secrets never reach the browser.

What can't a Server Component do?

Use state/effects/event handlers or browser APIs — it never hydrates. Interactivity must live in a Client Component leaf.

KEEP GOING

Another path next

View all

DSA Patterns

The 90-day pattern-based journey to Google-level DSA

Open

Computer Networks

How the Internet actually moves your data — visually

Open

Natural Language Processing

From raw text to Transformers, LLMs and production NLP systems

Open