cp .env.example .envpnpm installpnpm devThe docs will be served on localhost:3000/docs.
Search is implemented with pageFind which indexes built html files. To get it to work, run:
pnpm build
pnpm devThe docs use MDX.
Adding new content requires:
- YAML frontmatter
- A navigation entry in a
meta.tsfile - Content for the docs
Frontmatter looks like this. Title and description are mandatory.
---
title: "Introduction | Docs"
description: "This is a TypeScript agent framework. It helps you build AI applications and features quickly. It gives you the set of primitives you need: workflows, agents, RAG, integrations, syncs and evals."
---Navigation is defined in a relative meta.ts file. It modifies the title of the content in the sidebar:
const meta = {
overview: "Overview",
};
export default meta;This project is built on Nextra and therefore uses custom components that Nextra provides, including callouts, Tabs, etc.
You can find the full list here
Finding Something to Work On:
- Check the open issues labeled 'documentation' or 'good first issue'.
- Identify areas that are unclear, missing, or incorrect.
Making Changes:
- Create a new branch for your changes (
git checkout -b my-docs-update). - Make your desired edits to the documentation files (usually found in the
docs/endirectory). - Commit your changes with clear and concise messages.
Style Guide:
- Ensure your writing is clear, concise, and uses consistent formatting.
Submitting Changes:
- Push your branch to your fork (
git push origin my-docs-update). - Open a Pull Request (PR) against the main repository's
mainbranch. - Clearly describe the changes you've made in the PR description.
Review Process:
- Maintainers will review your PR.
- Address any feedback or requested changes.
- Once approved, your changes will be merged.
We appreciate your contributions to improving our documentation.