Hybrid rendering (static + server) in Astro

Introduction

Hybrid rendering lets you build web pages that combine fast static parts with dynamic server parts. This helps your site load quickly but still show fresh data.

You want a blog where most pages are static but comments load live.

You have a product page with mostly fixed info but live stock updates.

You want a landing page that loads fast but shows user-specific greetings.

You want to reduce server load by serving static content when possible.

Syntax

Astro

---
// Astro component frontmatter
const data = await fetch('https://api.example.com/data').then(res => res.json());
---
<html>
  <body>
    <h1>Static content here</h1>
    <p>Dynamic data: {data.value}</p>
  </body>
</html>

Use the frontmatter (---) to fetch server data asynchronously.

Static parts are written normally in the template outside the frontmatter.

Examples

This example shows a static title with a dynamic current time fetched on the server.

Astro

---
const time = new Date().toLocaleTimeString();
---
<html>
  <body>
    <h1>Static title</h1>
    <p>Current time: {time}</p>
  </body>
</html>

Here, the list of posts is fetched on the server and rendered dynamically, while the rest is static.

Astro

---
const posts = await fetch('https://api.example.com/posts').then(r => r.json());
---
<html>
  <body>
    <h1>Blog Posts</h1>
    <ul>
      {posts.map(post => <li>{post.title}</li>)}
    </ul>
  </body>
</html>

Sample Program

This Astro component fetches user data on the server and inserts the user's name into an otherwise static page. The header and footer stay the same for all visitors, making the page fast and efficient.

Astro

---
const user = await fetch('https://api.example.com/user').then(res => res.json());
---
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Hybrid Rendering Example</title>
  </head>
  <body>
    <header>
      <h1>Welcome to Our Site</h1>
    </header>
    <main>
      <p>Hello, {user.name}!</p>
      <p>This page is mostly static but shows your name dynamically.</p>
    </main>
    <footer>
      <small>© 2024 Example Corp</small>
    </footer>
  </body>
</html>

Important Notes

Hybrid rendering improves performance by serving static content quickly.

Use server code in frontmatter to fetch fresh data for dynamic parts.

Remember to keep static and dynamic parts clearly separated for best results.

Summary

Hybrid rendering mixes static and server-rendered content for speed and freshness.

Use Astro frontmatter to fetch data on the server side.

This approach is great for pages that mostly stay the same but need some live info.

Practice

1. What is the main benefit of using hybrid rendering in Astro?

easy

A. It only renders pages fully on the client side.

B. It combines fast static content with fresh server data.

C. It disables server-side rendering completely.

D. It requires no data fetching at all.

Solution

1. Step 1: Understand hybrid rendering purpose

   Hybrid rendering mixes static and server-rendered content to get the best of both worlds: speed and fresh data.

2. Step 2: Compare options

   Only 'It combines fast static content with fresh server data.' correctly describes this benefit. The other options misunderstand hybrid rendering.

3. Final Answer:

   It combines fast static content with fresh server data. -> Option B

4. Quick Check:

   Hybrid rendering = fast + fresh [OK]

Hint: Hybrid means mixing static speed with server freshness [OK]

Common Mistakes:

• Thinking hybrid disables server rendering
• Assuming hybrid is client-only rendering
• Believing hybrid needs no data fetching

2. Which Astro syntax correctly fetches data on the server side for hybrid rendering?

easy

A. fetch('https://api.example.com').then(data => setData(data))

B. const data = fetch('https://api.example.com')

C. ---
const data = await fetch('https://api.example.com')
---

D. useEffect(() => { fetch('https://api.example.com') })

Solution

1. Step 1: Identify Astro frontmatter usage

   Astro uses frontmatter (---) to run server-side code before rendering.

2. Step 2: Check options for server-side fetch

   --- const data = await fetch('https://api.example.com') --- uses frontmatter with await fetch, which is correct. The other options lack frontmatter or use client-side hooks.

3. Final Answer:

   ---\nconst data = await fetch('https://api.example.com')\n--- -> Option C

4. Quick Check:

   Server fetch = frontmatter + await [OK]

Hint: Use frontmatter (---) with await for server fetch [OK]

Common Mistakes:

• Omitting frontmatter for server code
• Using client hooks like useEffect in Astro
• Not awaiting fetch in server code

3. Given this Astro component code, what will be rendered?

---
const time = new Date().toLocaleTimeString();
---

  
    
Current Time:
    
{time}
  

medium

A. The time when the page was built (static time).

B. The current time updated every second.

C. An error because {time} is invalid syntax.

D. Nothing, because time is not defined.

Solution

1. Step 1: Understand Astro frontmatter timing

   Code inside frontmatter runs once at build or server render time, so time is fixed then.

2. Step 2: Check rendering behavior

   The rendered page shows the time captured during rendering, not live updates. So The time when the page was built (static time). is correct.

3. Final Answer:

   The time when the page was built (static time). -> Option A

4. Quick Check:

   Frontmatter time = fixed render time [OK]

Hint: Frontmatter runs once; time is static, not live [OK]

Common Mistakes:

• Thinking time updates live on client
• Confusing Astro syntax with React JSX
• Assuming {time} causes error

4. What is wrong with this Astro code snippet for hybrid rendering?

---
const data = fetch('https://api.example.com/data');
---
{data.json()}

medium

A. fetch is not awaited, so data is a Promise, causing an error.

B. Using fetch inside frontmatter is not allowed.

C. The <p> tag cannot contain JavaScript expressions.

D. data.json() returns a string, which cannot be rendered.

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise; without await, data is a Promise, not the response.

2. Step 2: Understand rendering error

   Calling data.json() on a Promise causes an error because data is not resolved yet.

3. Final Answer:

   fetch is not awaited, so data is a Promise, causing an error. -> Option A

4. Quick Check:

   Always await fetch in frontmatter [OK]

Hint: Always await fetch to get response, not Promise [OK]

Common Mistakes:

• Forgetting to await fetch
• Misunderstanding frontmatter fetch rules
• Thinking data.json() returns string directly

5. You want to build a blog page in Astro that shows static posts but also displays the current number of visitors fetched live from the server. Which approach best uses hybrid rendering?

hard

A. Render everything statically with no data fetching.

B. Fetch both posts and visitor count inside frontmatter only.

C. Fetch posts on client side with useEffect, visitor count in frontmatter.

D. Fetch posts in frontmatter for static build, then fetch visitor count inside a server component.

Solution

1. Step 1: Separate static and dynamic data

   Posts are mostly static, so fetching them in frontmatter for static build is efficient.

2. Step 2: Use server component for live data

   Visitor count changes often, so fetching it in a server component ensures fresh data on each request.

3. Step 3: Evaluate options

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. correctly mixes static and server rendering. The other options do not use hybrid rendering properly.

4. Final Answer:

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. -> Option D

5. Quick Check:

   Static + server fetch = hybrid rendering [OK]

Hint: Static data in frontmatter, dynamic in server component [OK]

Common Mistakes:

• Fetching all data statically losing freshness
• Fetching static data on client unnecessarily
• Not separating static and dynamic concerns