ContextBLOCK

Every file here is one package definition — a small YAML file describing where a library's documentation lives and how to build it. A daily job reads these, builds a searchable .db package from each, and publishes it so context install can fetch it.

Adding a library means adding one YAML file. No code.

Where the file goes

The directory name is the registry the package is distributed by, and the filename is the package name within it:

registry/npm/react.yaml          → npm/react
registry/pip/fastapi.yaml        → pip/fastapi
registry/npm/@trpc/server.yaml   → npm/@trpc/server     (scoped: use a subdirectory)

Go modules use the full module path, so every slash becomes a subdirectory:

registry/go/github.com/spf13/cobra.yaml   → go/github.com/spf13/cobra

Maven coordinates use _ in place of :, since : isn't filesystem-safe:

registry/maven/org.springframework.boot_spring-boot.yaml

If the project isn't distributed by a package manager at all — a language runtime, a daemon, a CLI tool — give it a directory named after the project containing a single self-named file. That's how the language runtimes are already done:

registry/python/python.yaml
registry/java/java.yaml

So Docker, Kubernetes, Podman and systemd would be registry/docker/docker.yaml, registry/kubernetes/kubernetes.yaml, and so on.

The name: field inside the file must match the path, or loading fails.

Which shape to use

A definition is either unversioned (one source:, always built from the current tip and published as latest) or versioned (a versions: list). Not both.

Unversioned — simplest, start here

name: drizzle-orm
description: "TypeScript ORM"
repository: https://github.com/drizzle-team/drizzle-orm

source:
type: git
url: https://github.com/drizzle-team/drizzle-orm-docs
docs_path: src/content/docs

Add ref: if the docs aren't on the default branch.

#