[DOC] Package search docs

[philipithomas]

No description provided.

[github-actions]

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)

[propel-code-bot]

Docs: Package Search and Code Collections Cloud Documentation

This PR adds extensive documentation about Chroma's Package Search feature, including user and API documentation for 'package-search' via the Model Context Protocol (MCP), registry reference, and a wide set of cloud and CLI documentation enhancements. Numerous new docs pages are introduced (including deep dives into forking, data model, architecture, package search registry, and CLI guides), with major refactoring and reorganization of existing files across the docs website. In addition, the codebase receives new UI components (e.g., combobox-steps, image-hover-text, steps) and next.js/Markdoc configuration changes to enable context-sensitive UI rendering. Many content files now include proper frontmatter (id and name), navigation sidebar and redirect configs have been updated, and a significant number of typos and formatting issues have been addressed for clarity and correctness.

Key Changes

• Added comprehensive documentation for Package Search MCP server usage, API reference, and supported registry packages in docs/docs.trychroma.com/markdoc/content/cloud/package-search/mcp.md and new registry.md.
• Introduced interactive step UI components (e.g., components/markdoc/combobox-steps.tsx, steps.tsx, combobox.tsx) to support dynamic documentation flows.
• Expanded and rewritten core documentation for architecture, data model, performance, pricing, migration, CLI usage, and integration guides, including extensive new frontmatter for navigation.
• Refactored sidebar and routing config to support new content structure (including forking and package search features).
• Upgraded and replaced several Radix UI dependencies; added @radix-ui/react-hover-card, updated dialog and popover versions for improved UI/UX.
• Added utility components for Python code block rendering (python-installation.tsx), image hover cards, and improved Markdoc code block styling.
• Revised and corrected code examples, code formatting, and provided more explicit step-by-step CLI/code usage in all areas.
• Migrated and standardized file frontmatter for all docs content, ensuring proper id and name properties for Markdoc/Next.js integration.
• Improved documentation clarity, fixed multiple typos and formatting/grammar issues across the documentation (including PR review suggestion fixes).

Affected Areas

• Documentation: All reference, cloud/product, and integration docs in markdoc/content and related config files
• Navigation: Sidebar structure (sidebar-config.ts) and middleware redirects
• User Interface: Docs UI components in components/markdoc/ and components/ui/
• Project Setup: Package manifest, Radix/UI and cmdk dependency updates (package.json, pnpm-lock.yaml)

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