Choosing the right framework for each island in Astro - Step-by-Step Execution

Concept Flow - Choosing the right framework for each island

Start: Identify UI parts

↓

Decide if static or interactive

↓

Static

↓

Combine islands into page

↓

Final page

This flow shows how to split a page into parts, decide which need interactivity, pick frameworks for those, and combine all into one page.

Execution Sample

Astro

const islands = [
  {name: 'Header', interactive: false},
  {name: 'Gallery', interactive: true, framework: 'React'},
  {name: 'Footer', interactive: false}
];

Defines page parts (islands) and marks which need interactivity and which framework to use.

Execution Table

Step	Island	Interactive?	Framework Chosen	Action
1	Header	No	None	Render as static HTML
2	Gallery	Yes	React	Render with React framework
3	Footer	No	None	Render as static HTML
4	Combine	N/A	N/A	Combine all islands into final page

💡 All islands processed and combined into final page

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
islands	[Header, Gallery, Footer]	[Header, Gallery, Footer]	[Header, Gallery, Footer]	[Header, Gallery, Footer]	[Header, Gallery, Footer]
renderedParts	[]	[Header as static HTML]	[Header static, Gallery React]	[Header static, Gallery React, Footer static]	[All combined into page]

Key Moments - 2 Insights

Why do some islands have no framework chosen?

Because those islands are static and don't need interactivity, so rendering plain HTML is enough (see execution_table steps 1 and 3).

How do we decide which framework to use for an interactive island?

We pick the framework best suited for that island's needs, like React for complex UI (see execution_table step 2).

Visual Quiz - 3 Questions

Look at the execution table, which island is rendered with React?

A Header

B Gallery

C Footer

D Combine

💡 Hint

Check the 'Framework Chosen' column in step 2

At which step do we combine all islands into the final page?

A Step 1

B Step 2

C Step 4

D Step 3

💡 Hint

Look for the 'Combine' action in the execution table

If the Gallery island was not interactive, what would change in the execution table?

A Gallery would be rendered as static HTML

B Gallery would still use React

C Footer would use React

D Header would become interactive

💡 Hint

Refer to how non-interactive islands are handled in steps 1 and 3

Concept Snapshot

Split page into islands by UI parts
Decide if each island is static or interactive
Render static islands as plain HTML
Use suitable framework for interactive islands
Combine all islands into one final page

Full Transcript

Choosing the right framework for each island means breaking a webpage into smaller parts called islands. Each island is checked if it needs interactivity. If not, it is rendered as simple static HTML. If yes, we pick a framework like React to render that island. Finally, all islands are combined to form the complete page. This approach helps optimize performance by only loading frameworks where needed.

Practice

1. What is the main reason to choose different frameworks for different islands in Astro?

easy

A. To optimize performance by loading only needed code for each island

B. To make the entire page load all frameworks at once

C. To force all islands to use the same framework

D. To avoid using any JavaScript on the page

Solution

1. Step 1: Understand what islands are in Astro

   Islands are small interactive parts of a page that can use different frameworks.

2. Step 2: Reason why different frameworks are chosen per island

   Choosing different frameworks lets you load only the code needed for each island, improving performance.

3. Final Answer:

   To optimize performance by loading only needed code for each island -> Option A

4. Quick Check:

   Performance optimization = B [OK]

Hint: Islands load only needed code to keep pages fast [OK]

Common Mistakes:

• Thinking all islands load all frameworks at once
• Believing islands must share the same framework
• Assuming no JavaScript is used at all

2. Which of the following is the correct way to specify a React island in Astro?

easy

A. <MyComponent client:react />

B. <MyComponent client:only='react' />

C. <MyComponent client:load />

D. <MyComponent client:hydrate />

Solution

1. Step 1: Recall Astro syntax for framework islands

   Astro uses client:only='react' to specify that the component should only load the React framework.

2. Step 2: Match the correct syntax for React island

   The correct syntax to specify a React island is client:only='react'.

3. Final Answer:

   <MyComponent client:only='react' /> -> Option B

4. Quick Check:

   Astro island syntax for React = A [OK]

Hint: Use client:only='react' to specify React islands [OK]

Common Mistakes:

• Using client:load without specifying framework
• Using client:react which is invalid
• Using client:hydrate which is invalid directive

3. Given this Astro island code:

<Counter client:load />

What happens when the page loads?

medium

A. The Counter component loads and runs JavaScript immediately on page load

B. The Counter component never loads JavaScript

C. The Counter component loads JavaScript only when visible on screen

D. The Counter component loads JavaScript only on user interaction

Solution

1. Step 1: Understand client:load behavior

   client:load means the island's JavaScript loads and runs as soon as the page loads.

2. Step 2: Apply this to the Counter component

   The Counter component will load and run its JavaScript immediately when the page loads.

3. Final Answer:

   The Counter component loads and runs JavaScript immediately on page load -> Option A

4. Quick Check:

   client:load = immediate JS load [OK]

Hint: client:load runs JS immediately on page load [OK]

Common Mistakes:

• Confusing client:load with client:visible or client:idle
• Thinking JS loads only on interaction
• Assuming no JS loads at all

4. You wrote this Astro island:

<MyWidget client:only='vue' />

But the widget does not load. What is the likely problem?

medium

A. Astro does not support Vue islands

B. client:only='vue' is invalid syntax

C. You must use client:load instead of client:only

D. You forgot to install the Vue integration in Astro

Solution

1. Step 1: Check if Vue integration is installed

   If the widget does not load, the most likely cause is forgetting to install the Vue integration in Astro.

2. Step 2: Confirm syntax

   client:only='vue' is valid syntax to specify Vue islands.

3. Final Answer:

   You forgot to install the Vue integration in Astro -> Option D

4. Quick Check:

   Missing integration = A [OK]

Hint: Install framework integrations to enable client:only usage [OK]

Common Mistakes:

• Forgetting to install Vue integration
• Thinking Astro doesn't support Vue
• Confusing client:load with client:only

5. You want to create a page with three islands: a React form, a Svelte chart, and a Vue button. How should you configure these islands in Astro for best performance?

hard

A. Load all frameworks globally in the main layout and use islands without client directives

B. Use client:load on all islands without specifying frameworks

C. Use React component with client:load, Svelte component with client:load, and Vue component with client:load on each island and install all three integrations

D. Use only one framework for all islands to avoid multiple integrations

Solution

1. Step 1: Identify the best practice for multiple frameworks

   Astro allows multiple frameworks per page by using components from each framework with client:load (or other) on each island and installing needed integrations.

2. Step 2: Avoid loading all frameworks globally or using client:load without framework

   Loading all globally wastes resources; use per-island components.

3. Step 3: Choose the correct approach

   Configure React form with client:load, Svelte chart with client:load, Vue button with client:load, with integrations for best performance.

4. Final Answer:

   Use React component with client:load, Svelte component with client:load, and Vue component with client:load on each island and install all three integrations -> Option C

5. Quick Check:

   Multiple frameworks per island = D [OK]

Hint: Use client:load with all needed integrations for multiple islands [OK]

Common Mistakes:

• Loading all frameworks globally wasting resources
• Using client:load without specifying framework
• Trying to use only one framework for all islands