feat(slides): create open source presentation for blueprint collaboration event

[AnirudhMahesh13]

Checklist

• I've thoroughly read the latest contribution guidelines.
• I've rebased my branch onto main before creating this PR.
• I've added tests to cover my changes (if applicable).
• I've verified that all new and existing tests have passed locally for mobile, tablet, and desktop screen sizes.
• My commit messages follow guidelines
• My change requires documentation updates.
• I've updated the documentation accordingly.
• My code follows existing patterns of this project and/or improves upon them.

---

Summary by CodeRabbit

• New Features

  • Rebranded the presentation with updated titles and refreshed content aligned with an open source theme.
  • Introduced a two-column layout with an embedded external link for enhanced information.

• Style / Visual Updates

  • Updated background graphics, transitions, and text styles to provide a more modern, visually appealing experience.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request rebrands the slide deck in apps/slides/slides.md to focus on open source and the Blueprint initiative. It updates key metadata—including the title, title template, and info section—and revises the layout to a two-column format with gap styling. The transition effect and background image are updated as well. Additionally, hackathon-specific details are removed and replaced with new content, including an embedded iframe, to align with the new thematic direction.

Changes

File(s)	Change Summary
apps/slides/slides.md	Updated title from "cuHacking" to "Intro to Open Source" and modified the title template and info section to match the Blueprint initiative; added a two-column layout with gap styling; changed the transition effect from "slide-left" to "fade-out"; updated the background image; removed hackathon-specific content and embedded a Blueprint iframe.

Poem

A fresh slide unfolds in digital light,
Titles morph to new visions, bold and bright.
Hackathon tales give way to open source dreams,
Blueprint ideas ripple like soft, sparkling streams.
With code and style in a seamless flight,
We celebrate change with a joyous byte!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46bf98d and 096306d.

📒 Files selected for processing (1)

• apps/slides/slides.md (3 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.