Pick a rendering strategy

• quiz
• medium
• server
• 10 min
• server-ssr
• mark done

Rendering strategy is the first decision in a frontend design, and every downstream choice inherits it. These four briefs each point at a different answer.

Documentation for an open-source library. Content changes when a release ships. Must rank in search.

• A SSR on every request
• B SSG at build time, rebuilt on release
• C Client-rendered behind an app shell
• D SSR with a 60-second edge cache

A logged-in analytics dashboard. Data is per-user, refreshed every few seconds, and behind auth.

• A SSG with client-side hydration
• B SSR on every request
• C Client rendering behind an app shell
• D SSG per user at build time

A news homepage. Content changes every few minutes, traffic spikes hard, and search matters.

• A SSG rebuilt every few minutes
• B Client rendering behind an app shell
• C SSR with a short edge cache and stale-while-revalidate
• D SSR with no cache

What is the cost of choosing SSR that teams most often discover late?

• A Search engines cannot index server-rendered HTML
• B Cache invalidation and server capacity become your problem, and personalisation fragments the cache
• C You cannot use a component framework
• D The bundle gets larger

Related

• Reading: SSR · SSG · App shell · SEO
• Playbook: Frontend system design
• Agent Skill: server-ssr