Deprecate Spanish Crowdin site translations#2410
Open
JFWooten4 wants to merge 9 commits into
Open
Conversation
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Remove the old announcement bar wrapper and config for translated pages. This was the Google Translate disclaimer that only rendered on `/es` routes. Caveat: the Google Translate navbar control still exists, but this disclaimer no longer displays because the Spanish Docusaurus routes have been removed. Co-authored-by: Codex <noreply@openai.com>
Contributor
Author
|
Slight misnomer in 0f8527b's desc. It was the CROWDIN disclaimer before, and there is now the Google bar on top in the commit. We could add a new disclaimer going forward (the logic still exists here), but since this was the only place it was used, I also dropped the Spanish-specific skeleton |
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.
This came up in #2404, based on prior discussion at #2233. The Google Translate feature has been working strong for months now, without any build or maintenance burden directly on the content side. Note 1 on my PR and the substance migration in #2409 imply that Bri's on the same side as us in the discussion, so I implemented the clean separation.