Skip to content

Conversation

c-gamble
Copy link
Contributor

No description provided.

@c-gamble c-gamble requested a review from jairad26 September 10, 2025 16:44
Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Copy link
Contributor

propel-code-bot bot commented Sep 10, 2025

Chroma Documentation: Major Overhaul, Structural & Copy Improvements, Markdoc Metadata Unification

This pull request is a sweeping, large-scale update to the Chroma documentation site and its underlying Markdoc structure. The changes unify and standardize frontmatter metadata (adding id and name fields to all Markdown content), improve language and organization throughout, fix inconsistencies and typos, expand or clarify sections, and update Markdown, TypeScript, and React files that integrate with the documentation. Markdoc config and presentation logic are updated to leverage these new metadata fields. Many functional and grammatical improvements are included for documentation accuracy, navigation, and user experience.

Key Changes

• Standardized frontmatter in all Markdoc Markdown files: adds id and name fields (removes/cleans up legacy fields)
• Rewrote and expanded the documentation navigation structure for deployment, integration, and core concept sections
• Fixed and clarified language, grammar, and spelling errors throughout docs, including resolving typos called out by bots
• Updated navigation and code samples for API, CLI, configuration, deployment, cloud, embedding providers, and SDKs
• Markdoc React/TSX components now receive and handle the new metadata; Combobox/Steps components expanded for UX and type flexibility
• Updated Markdoc config to recognize and require new id/name attributes, enabling better dynamic navigation and future structure-proofing
• Harmonized headings, code snippets, argument lists, and example blocks for major and minor guides (Python and TypeScript)
• Updated content organization relating to cloud/server/client deployment, CLI usage, collection management, and embedding function integration
• Refined pricing, roadmap, migration, architecture, troubleshooting, and reference documentation for clarity and completeness

Affected Areas

• Documentation site content: docs/docs.trychroma.com/markdoc/content/** (all major topics: Getting Started, Deployment, Integrations, Cloud, CLI, Concepts, Reference, etc.)
• Markdoc/Next.js React/TypeScript integration (components/markdoc/**/*.tsx, markdoc/config.ts, app page files)
• Documentation navigation and metadata system (frontmatter, file structure, Table of Contents)

This summary was automatically generated by @propel-code-bot

{% /Step %}

{% Step %}
In the Setting's menu, click on the {% ImageHoverText src="code-collections-api-keys.png" %}API Keys tab{% /ImageHoverText %}, and then on the {% ImageHoverText src="code-collections-api-keys.png" %}Create button{% /ImageHoverText %} to generate a key. Copy your API key, as you will need it to connect to the MCP server.
In the Settings menu, click on the {% ImageHoverText src="package-search-api-keys.png" %}API Keys tab{% /ImageHoverText %}, and then on the {% ImageHoverText src="package-search-api-keys.png" %}Create button{% /ImageHoverText %} to generate a key. Copy your API key, as you will need it to connect to the MCP server.
{% /Step %}

{% ComboboxEntry value="claude-code" label="Claude Code" %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Fix grammar: "Setting's" should be "Settings"

Context for Agents
[**Documentation**]

Fix grammar: "Setting's" should be "Settings"

File: docs/docs.trychroma.com/markdoc/content/cloud/package-search/mcp.md
Line: 42

- `local` - Instructs the CLI to find your collection on a local Chroma server at `http://localhost:8000`. If your local Chroma server is available on a different hostname, use the `host` argument instead.
- `host` - The host of your local Chroma server. This argument conflicts with `path`.
- `path` - The path of your local Chroma data. If provided, the CLI will use the data path to start a local Chroma server at an available port for browsing. This argument conflicts wth `host`.
- `theme` - The theme of your terminal (`light` or `dark`). Optimizes the UI colors for your terminal's theme. You only need to provide this argument once, and the CLI will persist it in `~/.chroma/config.json`.

{% TabbedUseCaseCodeBlock language="Terminal" %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Fix spelling error: "wth" should be "with"

Context for Agents
[**Documentation**]

Fix spelling error: "wth" should be "with"

File: docs/docs.trychroma.com/markdoc/content/docs/cli/browse.md
Line: 23

- `to-local` - Sets the copy target to a local Chroma server. By default, the CLI will try to find it at `localhost:8000`. If you have a different setup, use `path` or `host`.
- `to-cloud` - Sets the copy target to a DB on Chroma Cloud.
- `db` - The name of the Chroma Cloud DB with the collections you want to copy. If not provided, the CLI will prompt you to select a DB from those available on your active [profile](./profile).
- `host` - The host of your local Chroma server. This argument conflicts with `path`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Documentation]

Fix spelling error: "wth" should be "with"

Context for Agents
[**Documentation**]

Fix spelling error: "wth" should be "with"

File: docs/docs.trychroma.com/markdoc/content/docs/cli/copy.md
Line: 23

@c-gamble c-gamble merged commit 7d5777e into itai/code-collections-docs Sep 10, 2025
55 checks passed
@c-gamble c-gamble deleted the cooper/polish-package-search-docs branch September 10, 2025 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants