## Description
Add a build plugin (that only runs during `docusaurus build`) that
generates `llms.txt` files alongside each docs page with the contents of
each page.
More open in options:
<img width="322" height="294" alt="image"
src="https://github.com/user-attachments/assets/7029101d-6cf6-40ad-8c26-3878e288256a"
/>
New footer with link to llms.txt file:
<img width="361" height="73" alt="image"
src="https://github.com/user-attachments/assets/9885606f-dbde-4763-bfd1-4b711b3945c0"
/>
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
Fixes#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [X] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Per-page and site root llms.txt files are now generated for easier LLM
integration.
* Reworked page actions: a compact "Copy / Open in" menu provides quick,
data-driven links to external AI assistants and a direct llms.txt link.
* **Documentation**
* Standardized internal cross-reference links across storage and
observability docs.
* Clarified observability guidance and related warnings in multiple
storage pages.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
A first pass at removing tech debt from docs and enforcing consistent
styling through lint-staged and working prettier config.
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
Fixes#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
## Description
Migration of Nextra docs to Docusaurus.
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Removed a large set of docs in the docs-new directory, including
guides, examples, and reference pages across Agents, Auth, Deployment,
Examples, Evals, RAG, Memory, Observability, and Processors.
* **Chores**
* Updated redirect validation configuration source.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Paul Scanlon <pauliescanlon@gmail.com>
Co-authored-by: LekoArts <lekoarts@gmail.com>
## Description
This PR moves the doc content to a subdirectory. It also adds a redirect
to handle old links users have in their browser history.
Testing has been done on two links `installation` and `getting-started`
and they redirect properly.
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have performed a self-review of my own code
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have generated a changeset for this PR
---------
Co-authored-by: Brian Lou <brianlou2002@gmail.com>
Co-authored-by: Brian Lou <69982825+brian-lou@users.noreply.github.com>
Co-authored-by: archie-mckenzie <archie@generaltranslation.com>
Co-authored-by: NikAiyer <nick.aiyer@gmail.com>
Co-authored-by: Mrinank Bhowmick <77621953+Mrinank-Bhowmick@users.noreply.github.com>
Co-authored-by: Ehindero Israel <iehindero419@stu.ui.edu.ng>
Co-authored-by: Taofeeq Oluderu <oluderutaofeeq@gmail.com>
Co-authored-by: Marvin Frachet <marvin@mastra.ai>
Docs Migration to Nextra 4.
Nextra 4 includes support for:
1. NextJS App Router
2. Turbopack
3. Tailwind V4
4. A new search primitive, PageFind
Nextra new version deprecates some custom components and so we cannot
modify the `table-of-contents` component like we did in `v3` The only
settings provided are for modifying the toc itself rather than replacing
it:
https://nextra.site/docs/docs-theme/built-ins/layout#table-of-contents-toc
With this, the search should be better for custom components.