CodeNexus documentation hub

Documentation is being reorganized by product instead of one mixed runtime story.

`codenexus.cloud` remains the umbrella marketing surface for CodeNexus products. AutoDeployBase stays the primary product, while AIDOCS gets its own dedicated operator and reference documentation path as a sibling product.

Preferred documentation structure: docs.codenexus.cloud/autodeploybase and docs.codenexus.cloud/aidocs

Primary product

AutoDeployBase

The main CodeNexus application accelerator: scaffolding, plugins, deployment patterns, licensing, and production-ready app workflows.

Canonical docs path

docs.codenexus.cloud/autodeploybase

Quickstart, CLI, plugins, licensing, and deployment references

Architecture and validator/trust-boundary documentation

Primary product docs for CodeNexus application building

Open AutoDeployBase docs

Sibling product

AIDOCS

The AI-assisted docs, memory, routing, and MCP runtime layer. AIDOCS should stand on its own as a product and operator surface, not as an ADB feature subsection.

Preferred docs path

docs.codenexus.cloud/aidocs

Install, `/aidocs` entry flow, memory/session model, and CLI docs

Claude vs OpenCode integration guidance and host-specific caveats

MCP/runtime architecture, multilingual action tokens, and packaging boundaries

Review current AIDOCS docs shell

What changes from the old docs page

Start with the product that matches what you are trying to do today.

Use AutoDeployBase docs for app scaffolding, plugins, deployment, and product-building workflows.

Use AIDOCS docs for `/aidocs`, memory/session workflows, runtime behavior, and host integrations.

You can move between both doc paths without losing the bigger CodeNexus product picture.

Implementation next steps

New to CodeNexus? Start with AutoDeployBase docs if you are building an app.

Exploring docs-aware workflows? Start with AIDOCS.

Use the docs hub whenever you need to switch between product paths.

Explore the current AIDOCS overview