On this page
Codepot documentation
Codepot makes software intent explicit, reusable, and safe to generate. This documentation covers the supported OpenAPI and Jinja workflow, the official JavaScript runtime, and the final Rust language platform.
Choose where to begin
Build with supported packages
Use the current production-tested workflow when you need typed OpenAPI contracts and reusable Jinja generation today:
- Author contracts with codepot-openapi.
- Generate from OpenAPI with codepotg.
- Learn how the prototype workflow fits together.
Evaluate the official JavaScript runtime
Use the active workspace implementation when contributing to or testing the frontend-neutral rewrite:
- Understand codepotx.
- Compile typed authoring.
- Build and validate template packs.
- Plan and execute generation.
- Drive the runtime through codepotx-cli.
Explore the final platform
Read the platform documentation when working on the strongly typed language, compiler, CLI, LSP, extension, web tooling, or MCP integration:
Complete package documentation
Every active package has its own nested documentation tree and focused sidebar:
Package trees include getting started, architecture, configuration, complete feature explanations, template or API references, best practices, and troubleshooting.
Understand the ecosystem
Codepot develops features through a deliberate maturity path:
Read the ecosystem, choose a workflow, and architecture before deciding which layer belongs in a project.
Documentation behavior
The website precompiles Markdown, nested navigation, breadcrumbs, tables of contents, and search records during prepare:docs. Runtime requests do not scan the repository or parse Markdown files.
Use the left sidebar to move between topics, the package-focused sidebar inside package docs, the sticky page table of contents on desktop, and search to open pages or exact headings.