Improve homepage, use cases, features, and templates#734
Open
ashpreetbedi wants to merge 21 commits into
Open
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ashpreetbedi
marked this pull request as ready for review
July 19, 2026 20:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Use cases are a primary entry point for developers evaluating Agno. The navigation now leads with the product, workflow, and data-labeling paths where Agno has the clearest implementation story.
Each priority use case now identifies its target team, explains why the work matters, and names the Agno capabilities that make the implementation practical before moving into code.
The Feature pages now connect each capability to a concrete engineering or operational need. The Agent Platform guide follows a more useful development path from local setup through creation, improvement, evals, deployment, and ongoing operation.
The AgentOS Get Started flow now begins with a minimal runtime, proves it with a direct API request, explains how to connect and operate it, and separates runtime configuration from authentication and data isolation decisions.
The Templates section now helps developers choose a starting point before asking them to deploy. Application templates lead with the product and team they serve. Starter guides explain the real infrastructure, security, secret handling, and operating constraints for each provider.
Impact
Developers can identify the right Agno pattern earlier, understand why each platform capability matters, choose a suitable template, and follow a source-backed path from a local agent to a deployed and evaluated AgentOS system.
This is a documentation-only change. It does not change Agno runtime behavior or APIs.
Validation
81f50c2389e9710a3aab9fdd298a7215c264b986agno-agi/agentos-railwaystarterpython3 scripts/inventory/run_all.pypython3 scripts/check_install_coverage.pypython3 scripts/examples_sync/plan.pypython3 scripts/examples_sync/check_integrity.pymint broken-linksmint validategit diff --check