add-provider-doc

To generate provider documentation, you create usage docs in MDX format, add environment variable details, and update Docker configurations and image references. This structured workflow ensures consistent, repeatable documentation packages for new AI providers.

An end-to-end provider documentation bundle includes EN and CN usage guides, standardized environment variable details, Docker configuration templates, and organized image resources to support quick deployment and onboarding.

You set up bilingual usage documents by creating an English MDX file at docs/usage/providers/{provider-name}.mdx and a Chinese file at docs/usage/providers/{provider-name}.zh-CN.mdx, then applying the frontmatter-driven format.

Yes, you can use a frontmatter-driven format to enforce a consistent documentation structure. This approach ensures that environment variables, Docker configs, and usage guides remain standardized across all newly onboarded providers.

The best way to automate this is by using standardized templates that generate Docker configuration and environment variable docs simultaneously. This reduces manual errors and ensures all required deployment references are prepared.

Provider onboarding docs lack consistency when they are not generated using a structured, frontmatter-driven format and standardized resource templates. Automating the end-to-end workflow enforces a repeatable structure and reduces onboarding errors.