docs: add Longbridge Developers product documentation style guide#1156
Open
endless-bot wants to merge 4 commits into
Open
docs: add Longbridge Developers product documentation style guide#1156endless-bot wants to merge 4 commits into
endless-bot wants to merge 4 commits into
Conversation
endless-bot
changed the title
…gbridge Developers 构建一个产品文档指引、规范。 https://de Generated by Endless task #38. Co-authored-by: Huacnlee Li Huashun <huacnlee@longbridge-inc.com>
endless-bot
changed the title
…gbridge Developers 构建一个产品文档指引、规范。 https://de Generated by Endless task #38. Co-authored-by: Huacnlee Li Huashun <huacnlee@longbridge-inc.com>
endless-bot
changed the title
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.
🤖 Auto-generated by Endless task #38.
Initiated by: huacnlee@longbridge-inc.com
docs/en/docs/style-guide/covering content types, writing guidelines, information architecture, API reference standards, and multilingual strategy, modelled after Cloudflare's Product Docs Content Strategycontent-types.mddefining canonical doc formats (concept, tutorial, how-to, reference) with usage criteria and structural templateswriting-guidelines.mdandinformation-architecture.mdto establish tone, terminology, navigation hierarchy, and page structure conventions for Longbridge Developersapi-reference.mdandmultilingual.mdto standardise how REST/SDK references are documented and how content should be adapted across supported languagesspecs/2026-07-14-content-strategy.mdas the backing product requirement document capturing rationale, scope, and acceptance criteria for the entire initiative