Add localization plugin and initial es translation
#1011
Merged
Conversation
This file contains 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
coppolaemilio
added
topic:backend
coppolaemilio
changed the title
es translationes translation
paddy-exe
added a commit
to paddy-exe/godot-website
that referenced
this pull request
Feb 28, 2025
Based on the localization support from godotengine#1011
paddy-exe
added a commit
to paddy-exe/godot-website
that referenced
this pull request
Feb 28, 2025
Based on the localization support from godotengine#1011
paddy-exe
added a commit
to paddy-exe/godot-website
that referenced
this pull request
Feb 28, 2025
Based on the localization support from godotengine#1011 First feedback
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.
I've started adding localization support directly in Jekyll but with a custom made plugin.
Initially, the idea was to transition the website to Hugo because of how long it is taking to build from scratch and the existing localization plugins duplicating every collection item for each language. So the current plan now is to just translate the main pages to other languages and keep the posts in English (as it is highly unlikely that we'll ever translate blogposts).
With this new method, we don't need to port the website to Hugo, and we can keep the localized pages to only the ones that we care about without adding a significant increase time in builds.
The current proof of concept is translating part of the home page to Spanish, but there are a few things missing from the localization that should be addressed in further commits to this PR or in future ones.
The localization files are currently
.ymlfiles at/_i18nES version of the site:
The to-do items currently are:
Closes #814