Removed v0.0.3b from docs

[NiveditJain]

No description provided.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated documentation across multiple sections by removing beta status labels and notes. Docker Compose setup, Exosphere features (concepts, graph components, triggers), and Python SDK documentation now reflect stable, production-ready status.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The pull request removes all beta-related guidance and notices from documentation files, including beta version setup instructions, status warnings, and inline beta references across Docker Compose setup and Exosphere feature documentation.

Changes

Cohort / File(s)	Summary
Docker Compose Setup Documentation docs/docs/docker-compose-setup.md	Removed entire Beta Version guidance section including environment variable examples (.env, export) and beta-latest Docker tag setup instructions.
Exosphere Concept & Feature Documentation docs/docs/exosphere/concepts.md, docs/docs/exosphere/graph-components.md, docs/docs/exosphere/triggers.md	Removed beta-feature notices and status warnings (beta-latest Docker tag and SDK version 0.0.3b1 references) from Automatic Triggers section, Triggers section, and Triggers documentation respectively.
Exosphere SDK Documentation docs/docs/exosphere/python-sdk-graph.md	Removed inline beta comment from the triggers parameter in upsert_graph call documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~10 minutes

Possibly related PRs

• Docs update for setup #347: Modifies Docker Compose setup and Beta Version guidance documentation, directly related to the same beta reference removals.
• Updated readme #640: Includes overlapping documentation removals targeting Docker Compose guidance and beta-related references.

Suggested labels

documentation

Poem

🐰 Beta's farewell, no longer so bold,
The docs now shine, polished and gold,
No "experimental" warnings to see,
Just stable guidance, finally free! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cadfc99 and 6606487.

📒 Files selected for processing (5)

• docs/docs/docker-compose-setup.md
• docs/docs/exosphere/concepts.md
• docs/docs/exosphere/graph-components.md
• docs/docs/exosphere/python-sdk-graph.md
• docs/docs/exosphere/triggers.md

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @NiveditJain, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a comprehensive update and refinement of the project's documentation, particularly the main README.md and index.md files. The changes aim to provide a clearer, more user-friendly introduction to Exosphere by updating the project's core messaging, removing outdated beta references, and restructuring content into more accessible formats like tables and feature cards. These updates are designed to enhance the onboarding experience for new users and present a more polished overview of Exosphere's capabilities as a reliability runtime for AI agents.

Highlights

• Documentation Refinement: The primary documentation files, README.md and index.md, have undergone a significant overhaul to improve clarity, structure, and overall user experience. This includes a revised project description and a more engaging presentation of features.
• Removal of Beta References: All explicit mentions and instructions related to the v0.0.3b beta version and beta-latest Docker tags have been systematically removed across the documentation, indicating a move towards a stable release or a streamlined focus.
• Content Restructuring and Styling: Feature lists and core concepts are now presented in more digestible formats, such as markdown tables and new 'feature card' layouts, replacing previous lengthy bulleted lists. This is supported by new CSS rules for improved visual presentation.
• Navigation and Messaging Updates: The mkdocs.yml navigation has been updated to reflect the new content organization and terminology, with a shift in the project's core messaging from 'Distributed AI Workflow Infrastructure' to 'Reliability Runtime for AI Agents'.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully removes all references to the beta version v0.0.3b from the documentation, which aligns with the PR's goal. It also includes a significant and well-executed refactoring of the main README.md and the documentation's index page, introducing a cleaner, more structured layout with new CSS. My review includes a couple of suggestions to further improve the user experience for new developers and enhance the maintainability of the documentation's styling.

I am having trouble creating individual review comments. Click here to see my feedback.

README.md (39-46)

The new README is much cleaner and more structured. However, by removing the 'Quick Start' and 'Getting Started' sections with code examples (especially the docker-compose one), we might be making it harder for new users to quickly try out Exosphere. A concise quick start guide on the main README is a very effective way to engage developers.

Consider re-adding a minimal 'Quick Start' section that shows how to get Exosphere running in a couple of commands. The previous docker-compose example was great for this.

docs/docs/index.md (1-3)

For better maintainability and separation of concerns, it's recommended to avoid inline styles and legacy HTML attributes like align="center". You can move this styling to extra.css using classes. This keeps your content clean and centralizes styling rules.

Suggestion:

First, apply the code suggestion below to this file.

Then, add the corresponding styles to docs/docs/stylesheets/extra.css:

.logo-container {
  text-align: center;
}
.logo-main {
  max-width: 50%;
}

<p class="logo-container">
<img src="assets/logo-with-bg.png" alt="exosphere logo" class="logo-main">
</p>