Conversation
RayBB
force-pushed
the
remove-translated-readmes
branch
from
5919e81 to
84c9ebc
Compare
bhardwajparth51
pushed a commit
to bhardwajparth51/openlibrary
that referenced
this pull request
Mar 3, 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
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.
I’m currently focused on cleaning up and organizing our documentation to make it more consistent and maintainable.
At the moment, the translated README files don’t have a defined place in our documentation system. As we’ve seen with the version that hasn’t been meaningfully updated in over four years, these files tend to go unmaintained. This creates ongoing overhead for the team with very limited benefit, especially given how easily documentation can now be translated using automated tools.
For that reason, I recommend we remove the translated READMEs for now. Our priority should be maintaining high-quality, up-to-date English documentation. Once that foundation is solid, we can revisit translation options and explore sustainable, possibly automated approaches.
As documentation lead, that’s the direction I believe we should take.
Technical
Testing
Screenshot
Stakeholders