Repository navigation
docs: add bilingual documentation and Collaborative branding - #6
Merged
Merged
Conversation
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
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.
Collaborative now has an English-first public README and documentation site, with a matching Russian version. The language switcher keeps the current documentation page and section; search and navigation follow the selected language. Package guides, setup and deployment examples, security guidance, OpenAPI descriptions, route matrices, and SDK/Kit references are included.
Adds the Collaborative vector logo, light/dark wordmarks, and a repository social cover. Removes references to asmblyr.io from public documentation and corrects stale descriptions of Core routing, SDK generation, and prepared plugin forms. The application, admin routes, existing i18next catalogs, and API locale defaults are unchanged.
Reference generation checks locale coverage and missing translations while keeping API schemas, identifiers, and examples intact. OpenAPI still labels incomplete operations as route-only; Swagger request execution remains disabled.
Validation:
pnpm format:check,pnpm publication:check, and Git whitespace checks passed.