Adding Translations for API Documentation Content#400
Merged
sachin-panayil merged 8 commits intomainfrom Feb 20, 2026
Merged
Conversation
rmillergv
approved these changes
Feb 19, 2026
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.
Warning
This PR should be merged after #399
Adding Translations for API Documentation Content
Problem
Not ticketed but thought it would be a good time to introduce this solution. We currently do not support multiple languages for our API documentation and drf-spectacular does not natively handle this.
Solution
Using Django's native translation library, translate content into different language that is read/displayed at runtime
Result
Swagger and ReDoc now supports multiple languages
Some important notes regarding the summary line:
Test Plan
make upmake test