Hybrid rendering (static + server) in Astro - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is hybrid rendering in Astro?

Hybrid rendering in Astro means combining static site generation with server-side rendering. Some parts of the page are built once and served as static files, while others are rendered on the server when requested.

beginner

Why use hybrid rendering instead of only static or only server rendering?

Hybrid rendering lets you get the speed of static pages for most content and the flexibility of server rendering for dynamic parts. This balance improves performance and user experience.

intermediate

How does Astro decide which parts to render statically and which on the server?

Astro lets you mark components or pages to be statically generated or server rendered. You choose based on how often content changes or needs user-specific data.

beginner

What is a real-life example of hybrid rendering in a website?

Imagine a blog: the posts are static because they rarely change, but the comments section is server rendered to show live updates and user input.

intermediate

How does hybrid rendering affect SEO and page load speed?

Static parts load very fast and are easy for search engines to read, improving SEO. Server-rendered parts can show fresh data without slowing down the whole page.

What does hybrid rendering combine in Astro?

A Only client-side rendering

B Client-side rendering and server-side rendering

C Only static site generation

D Static site generation and server-side rendering

Hybrid rendering mixes static site generation with server-side rendering to get benefits of both.

Which part of a hybrid rendered site is best for content that rarely changes?

A Static generated pages

B Server-side rendered components

C Client-side rendered widgets

D Dynamic API calls

Static generated pages are best for content that rarely changes because they load fast and are cached.

In Astro, how do you specify a component to be server rendered?

A By writing it in plain HTML

B By using the <Static> tag

C By marking it with server directive or exporting server code

D By importing it from a client library

Astro uses directives or exports to mark components for server rendering.

What is a benefit of hybrid rendering for SEO?

A Static parts load fast and are easy to index

B Hybrid rendering hides content from search engines

C Client-side rendering improves SEO

D Server parts block search engines

Static parts load quickly and are fully rendered in HTML, making them easy for search engines to index.

Which scenario fits hybrid rendering best?

A A dashboard with only live data

B A blog with static posts and live comments

C A single-page app with no server

D A static brochure site with no dynamic content

Hybrid rendering suits sites mixing static content and dynamic parts like live comments.

Explain how hybrid rendering works in Astro and why it is useful.

Think about how some parts of a page can be fixed and others change often.

Describe a real-world website example where hybrid rendering would improve user experience.

Consider a blog or e-commerce site with both fixed and changing content.

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