Yilialinn opened a new pull request, #2120: URL: https://github.com/apache/apisix-website/pull/2120
Changes: - Clarify the Apache APISIX AI Gateway hub's supported capabilities and responsibility boundaries. - Map multi-provider proxying, retries, rate limiting, prompt controls, RAG, semantic routing, response caching, Lakera Guard integration, and gateway-level observability to current APISIX plugin documentation. - Separate the search intent of the AI Gateway hub, the introductory guide, and the AI Gateway vs API Gateway comparison in both English and Chinese. - Add contextual links between the hub and supporting articles, plus desktop and mobile regression coverage. - Remove unsupported provider-count wording and the inaccurate implication that Apache APISIX provides an MCP Gateway capability. Validation: - `yarn lint:frontmatter` - `yarn --cwd next sync` - `npm --prefix next run check` - `NODE_OPTIONS=--max-old-space-size=3072 npm --prefix next run build` - Targeted Playwright tests on desktop and mobile: 24 passed, 2 skipped - English blog preview build - Independent content, technical accuracy, and SEO review: 9.3/10 with no P0-P3 findings - `git diff --check` Notes: - The AI Gateway hub title, H1, URL, canonical, and hreflang remain unchanged. - No API7 commercial content is introduced. - Apache APISIX is not described as providing an MCP Gateway. - The existing plugin documentation canonical strategy is unchanged. - The legacy Chinese Docusaurus-only build remains blocked by malformed URLs in two unrelated historical posts outside this diff. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
