Why SSR enables dynamic content in Astro - Visual Breakdown

Concept Flow - Why SSR enables dynamic content

User requests page

↓

Server runs SSR code

↓

Fetch dynamic data

↓

Generate HTML with data

↓

Send HTML to browser

↓

Browser shows page with fresh content

This flow shows how the server creates a fresh page with up-to-date data each time a user asks for it.

Execution Sample

Astro

export async function get() {
  const data = await fetchData();
  return {
    body: `<h1>${data.title}</h1>`
  };
}

This code fetches data on the server and returns HTML with that data for the browser.

Execution Table

Step	Action	Data State	Output HTML
1	User requests page	No data yet	No output yet
2	Server runs get() function	No data yet	No output yet
3	Fetch dynamic data	Data fetched: {title: 'Hello'}	No output yet
4	Generate HTML with data	Data available	<h1>Hello</h1>
5	Send HTML to browser	Data available	<h1>Hello</h1>
6	Browser renders page	Data available	Page shows 'Hello'

💡 Process ends after sending the generated HTML to the browser.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
data	undefined	{title: 'Hello'}	{title: 'Hello'}	{title: 'Hello'}
outputHTML	''	''	<h1>Hello</h1>	<h1>Hello</h1>

Key Moments - 2 Insights

Why does the server fetch data every time a user requests the page?

Because SSR runs the code on each request (see execution_table step 3), it can get fresh data to show dynamic content.

Why is the HTML generated on the server and not in the browser?

Generating HTML on the server (step 4) means the browser receives a ready page with current data, improving speed and SEO.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'data' after step 3?

A {title: 'Hello'}

B undefined

C ''

D <h1>Hello</h1>

💡 Hint

Check the 'Data State' column at step 3 in the execution_table.

At which step does the server send the HTML to the browser?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column in the execution_table for sending HTML.

If the data changes on the server, how does SSR show updated content?

A By caching old HTML

B By fetching new data on each request

C By running code only once

D By letting the browser update HTML

💡 Hint

Refer to the 'Fetch dynamic data' step in the execution_table.

Concept Snapshot

SSR means the server builds the page each time a user asks.
It fetches fresh data and creates HTML with it.
This lets the page show up-to-date, dynamic content.
The browser gets ready HTML, so it loads fast and is SEO-friendly.

Full Transcript

When a user requests a page, the server runs code to fetch fresh data. Then it builds HTML using that data. This HTML is sent to the browser, which shows the page with the latest content. This process is called Server-Side Rendering or SSR. It enables dynamic content because the server can get new data on every request and create a page that matches it. This is faster for users and better for search engines because the page is ready to view immediately.

Practice

1. Why does Server-Side Rendering (SSR) enable dynamic content in web pages?

easy

A. Because SSR caches pages permanently and never updates them.

B. Because SSR sends a static HTML file that never changes after deployment.

C. Because SSR runs all JavaScript only in the browser after loading the page.

D. Because SSR builds the page on the server each time a user requests it, allowing fresh data.

Solution

1. Step 1: Understand SSR page generation

   SSR builds the page on the server every time a user visits, not just once.

2. Step 2: Connect SSR to dynamic data

   This means the server can include fresh or user-specific data before sending the page.

3. Final Answer:

   Because SSR builds the page on the server each time a user requests it, allowing fresh data. -> Option D

4. Quick Check:

   SSR = fresh server-built pages [OK]

Hint: SSR builds pages on demand, so content can change [OK]

Common Mistakes:

• Thinking SSR sends static files only
• Confusing SSR with client-side rendering
• Assuming SSR caches pages forever

2. Which of the following is the correct way to enable SSR in an Astro component?

easy

A. export const prerender = true;

B. export const prerender = false;

C. import prerender from 'astro';

D. const prerender = 'enabled';

Solution

1. Step 1: Recall SSR enabling syntax in Astro

   Astro uses export const prerender = false; to enable server-side rendering.

2. Step 2: Check other options for correctness

   Exporting prerender = true; results in static rendering, the import is invalid, and the const assignment uses wrong syntax.

3. Final Answer:

   export const prerender = false; -> Option B

4. Quick Check:

   SSR enabled by export const prerender = false; [OK]

Hint: Look for exact prerender export syntax in Astro [OK]

Common Mistakes:

• Using prerender = true instead of false to enable SSR
• Trying to import prerender as a module
• Assigning prerender as a string instead of boolean

3. Given this Astro component code with SSR enabled:

export const prerender = false;
const time = new Date().toLocaleTimeString();
---
<div>Current time: {time}</div>

What will the user see when they reload the page multiple times?

medium

A. The time shown updates on each reload to the current server time.

B. The time shown is fixed to when the page was first built and never changes.

C. The time updates only after client-side JavaScript runs.

D. The page will show an error because Date is not allowed in SSR.

Solution

1. Step 1: Understand SSR effect on dynamic values

   With prerender = false, the server runs the code on each request, so new Date() is fresh every time.

2. Step 2: Predict output on reload

   Reloading the page triggers server to build new HTML with current time, so time updates.

3. Final Answer:

   The time shown updates on each reload to the current server time. -> Option A

4. Quick Check:

   SSR runs code fresh each request [OK]

Hint: SSR runs code on server per request, so output changes [OK]

Common Mistakes:

• Thinking time is fixed after first build
• Assuming client JS updates time instead
• Believing Date is disallowed in SSR

4. This Astro component is intended to show the current user name dynamically using SSR:

export const prerender = false;
const userName = fetchUserName();
---
<div>Hello, {userName}!</div>

But it shows "Hello, undefined!" What is the likely problem?

medium

A. Astro does not support variables in templates.

B. SSR is disabled by default, so dynamic code does not run.

C. fetchUserName() is asynchronous but used without await.

D. The variable userName must be declared inside the template.

Solution

1. Step 1: Identify async function usage

   fetchUserName() likely returns a Promise, so it must be awaited to get the value.

2. Step 2: Understand why undefined appears

   Without await, userName is a Promise object, which renders as undefined in template.

3. Final Answer:

   fetchUserName() is asynchronous but used without await. -> Option C

4. Quick Check:

   Async functions need await to get values [OK]

Hint: Await async calls to get real values in SSR [OK]

Common Mistakes:

• Forgetting to await async functions
• Assuming SSR is off by default
• Thinking variables must be inside template tags

5. You want to show a personalized greeting on your Astro page that updates every time a user visits, using SSR. Which approach correctly achieves this?

export const prerender = false;
async function getUserName() {
  return await fetch('/api/user').then(res => res.json()).then(data => data.name);
}
const userName = await getUserName();
---
<h1>Welcome back, {userName}!</h1>

Why does this work to show dynamic content?

hard

A. Because SSR runs the async function on the server per request, fetching fresh user data each time.

B. Because Astro caches the userName forever after first fetch, so it never changes.

C. Because the client browser runs getUserName() after page loads to update content.

D. Because SSR disables async functions to improve performance.

Solution

1. Step 1: Analyze async data fetching in SSR

   The async function runs on the server every time a user requests the page, so it fetches fresh data.

2. Step 2: Understand dynamic content generation

   Since SSR builds the page per request, the greeting updates with the latest user info.

3. Final Answer:

   Because SSR runs the async function on the server per request, fetching fresh user data each time. -> Option A

4. Quick Check:

   SSR + async fetch = fresh dynamic content [OK]

Hint: SSR runs async code fresh on server per request [OK]

Common Mistakes:

• Thinking Astro caches async results forever
• Assuming client runs async fetch after load
• Believing SSR disables async functions