docs: route Cherry Studio into integrations - #84
Open
acedatacloud-dev wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependency
This PR is stacked on #83, which introduces the safe
integrationsdocument-only namespace. This relative diff adds only Cherry Studio.Why
PlatformBackend already contains a substantial Cherry Studio guide covering custom-provider URL semantics, model-family endpoints, image generation, token setup, usage history, limitations, and troubleshooting. The Docs generator cannot currently assign that platform-level document to a stable integration path, so the content remains outside the Docs tree.
What changed
development_cherry_studiotoguides/integrations/cherry-studio.mdx;development_cherry_studioas the canonical platform document alias;Validation
docs/publish-open-webui-guide— 2 files, 15 linesgit diff --check— cleanGeneration / rollout
After the base and this PR merge, the protected Docs sync generates localized MDX from PlatformBackend and the Translation API. Generated files are intentionally not hand-edited here. Navigation follows only after generated files exist.
Scope boundaries
This PR adds only the Cherry Studio record. It does not modify the guide, generated MDX, Open WebUI, LobeChat, platform APIs, or client behavior.
Rollback
Revert this mapping commit; the source guide remains in PlatformBackend.
🤖 Generated with Claude Code