docs: Add discord link to Community page in docs #2157
Conversation
The mkdocstrings plugin was configured with 'paths: [src]' but the actual source code is located at 'ragas/src' relative to the mkdocs.yml file. This was causing build failures with errors like: - 'ragas.cache could not be found' - 'ragas.embeddings could not be found' The fix updates the path to 'ragas/src' which allows mkdocstrings to properly generate API documentation when running 'mkdocs serve' locally. Resolves mkdocstrings module import errors during local documentation development.
…ion to core_concepts - Reorder experimental tutorials in mkdocs.yml to follow logical progression: Prompt → RAG → Workflow → Agent (instead of Agent being first) - Rename docs/experimental/explanation/ to core_concepts/ for consistency - Update navigation links and section titles to match new structure - Fix 'Next' button navigation to follow intended learning path Fixes navigation issue where 'Next' from tutorials index went to Agent instead of starting with Prompt tutorial.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Greptile Summary
This PR enhances the community documentation by adding a Discord section and making a minor punctuation improvement. The main change introduces a new "Discord community" section positioned prominently near the top of the community page, providing users with a direct link to join the Ragas Discord server at https://discord.com/invite/5djav8GGNZ. This addition serves to connect developers, facilitate idea sharing, and provide community support channels.
The change fits well within the existing community documentation structure, which already emphasizes collaboration and knowledge sharing through contributors, blog insights, and events. By placing the Discord section early in the document (after the overview but before contributors), it ensures high visibility for this real-time communication channel. The PR also includes a small punctuation enhancement by adding an exclamation mark to the Contributors section header, making it more welcoming and enthusiastic.
These changes align with the community page's stated purpose of fostering collaboration and providing resources for community engagement. The Discord integration represents a natural extension of the existing community infrastructure, offering immediate support and discussion opportunities that complement the existing blog posts, contributor profiles, and event listings.
Confidence score: 5/5
- This PR is safe to merge with minimal risk as it only adds documentation content without affecting any code functionality
- Score reflects simple, low-risk documentation changes that enhance community engagement without introducing technical complexity
- No files require special attention as this is a straightforward documentation update
1 file reviewed, no comments
dosubot
bot
added
the
size:XS
|
also I think the mkdocs navbar title is missing a "❤️" in front of it - matching with the title |
No description provided.