Skip to content

docs: integrate Scion explainer slideshow directly into landing page#287

Merged
ptone merged 2 commits into
GoogleCloudPlatform:mainfrom
ptone:scion/dev-docs-landing
Jun 1, 2026
Merged

docs: integrate Scion explainer slideshow directly into landing page#287
ptone merged 2 commits into
GoogleCloudPlatform:mainfrom
ptone:scion/dev-docs-landing

Conversation

@ptone
Copy link
Copy Markdown
Member

@ptone ptone commented Jun 1, 2026

Summary

  • Integrates the Scion explainer slideshow directly into the landing page as an interactive HTML iframe element.
  • Updates the project design logs to document the inline slideshow integration.

Test plan

  • Verify the landing page renders the slideshow element correctly.
  • Confirm responsive layout for mobile viewport displays.

ptone added 2 commits May 31, 2026 20:08
Replace the iframe-embedded slide deck with a fully inline, interactive
slideshow component. All 7 slides from the hosted deck are now rendered
directly in the landing page with scoped CSS and inline JavaScript.

Key changes:
- Full slideshow with keyboard/touch/click navigation, progress dots,
  and animated transitions
- All interactive widgets recreated inline: State Model Simulator,
  Collaborators Graph (with dynamic spawn/delete loop), Reactive
  Notification Wakeup flow, and Shared Filesystem Simulator
- Replace "Boot" with "Run" throughout all slide content
- Remove Overview Deck iframe section; add "technical deep dive" link
  to the Google Slides deck below the inline slideshow
- Move "How it works" quickstart section below "See it in Action" video
- Scope all slideshow CSS under .scion-deck to avoid style conflicts
  with the landing page
@ptone ptone merged commit a5a8663 into GoogleCloudPlatform:main Jun 1, 2026
7 of 9 checks passed
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the project log documentation to reflect the integration of an interactive inline slideshow component into the docs-site landing page, replacing the previous iframe embed approach. The feedback suggests minor formatting and grammatical improvements in the markdown file, specifically wrapping the command curl in backticks and adding the article "the" before "file structure" for better readability.

- The slides were fetched via curl since the WebFetch tool had model availability issues.
- Node.js 22+ was required for the Astro build, which wasn't available in the sandbox. Validated the file structure (frontmatter syntax, balanced HTML tags) programmatically instead.
- The landing page is a standalone Astro page (not a Starlight content doc), so it uses raw HTML/CSS rather than MDX components.
- The slides HTML/CSS/JS were fetched via curl (WebFetch tool had model availability issues) and carefully adapted for inline embedding.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and consistency with standard markdown formatting, consider wrapping the command-line tool curl in backticks.

Suggested change
- The slides HTML/CSS/JS were fetched via curl (WebFetch tool had model availability issues) and carefully adapted for inline embedding.
- The slides HTML/CSS/JS were fetched via `curl` (WebFetch tool had model availability issues) and carefully adapted for inline embedding.

- Node.js 22+ was required for the Astro build, which wasn't available in the sandbox. Validated the file structure (frontmatter syntax, balanced HTML tags) programmatically instead.
- The landing page is a standalone Astro page (not a Starlight content doc), so it uses raw HTML/CSS rather than MDX components.
- The slides HTML/CSS/JS were fetched via curl (WebFetch tool had model availability issues) and carefully adapted for inline embedding.
- Node.js 22+ was required for the Astro build, which wasn't available in the sandbox. Validated file structure (balanced HTML tags, frontmatter syntax) programmatically.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Adding the article 'the' before 'file structure' improves the grammatical flow of the sentence.

Suggested change
- Node.js 22+ was required for the Astro build, which wasn't available in the sandbox. Validated file structure (balanced HTML tags, frontmatter syntax) programmatically.
- Node.js 22+ was required for the Astro build, which wasn't available in the sandbox. Validated the file structure (balanced HTML tags, frontmatter syntax) programmatically.

krohnjw pushed a commit to ParkWhiz/scion that referenced this pull request Jun 3, 2026
…oogleCloudPlatform#287)

* Integrate Scion explainer slideshow directly into landing page

Replace the iframe-embedded slide deck with a fully inline, interactive
slideshow component. All 7 slides from the hosted deck are now rendered
directly in the landing page with scoped CSS and inline JavaScript.

Key changes:
- Full slideshow with keyboard/touch/click navigation, progress dots,
  and animated transitions
- All interactive widgets recreated inline: State Model Simulator,
  Collaborators Graph (with dynamic spawn/delete loop), Reactive
  Notification Wakeup flow, and Shared Filesystem Simulator
- Replace "Boot" with "Run" throughout all slide content
- Remove Overview Deck iframe section; add "technical deep dive" link
  to the Google Slides deck below the inline slideshow
- Move "How it works" quickstart section below "See it in Action" video
- Scope all slideshow CSS under .scion-deck to avoid style conflicts
  with the landing page

* Update project log for inline slideshow integration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant