Closed spier closed 10 months ago
Neat! Is this basically the same idea and setup of what is done for the translation of the Patterns book?
Neat! Is this basically the same idea and setup of what is done for the translation of the Patterns book?
It is similar but not quite the same. In both cases we use the collections/versioning feature of gitbook. The he difference in implementation is:
1) patterns - all languages merged into main
branch. versions deployed from different folders.
2) managing ISP - languages kept in different branches
Approach (2) was the easiest to do a quick test deployment that the translators can review. However long-term I like the approach (1) better as it allows you to see original and translation side-by-side, prevents long-lived branches, and allows us to acknowledge all contributors in the mainline.
Maybe a bit more information than you were looking for but doesn't hurt to document it :)
This is great.
FYI this PR won't actually be merged into main
, as it would overwrite the English files of the book.
We only needed this PR to show the status of development and support the conversation.
I am therefore closing this PR, so that it does not get merged accidentally.
The Galician translation of the book is published from the translation-gl
branch itself.
This is now live at: https://innersourcecommons.gitbook.io/managing-innersource-projects/v/gl/
A couple of notes from the implementation of this:
Things left to do (for future PRs):
translation-gl
main
. That allows us to attribute the contributors correctly and show them in the overview of contributors. We could take some inspiration from the InnerSourcePatterns repo for this
Closes #60.
This working is still in a draft stage, as I am only using this branch to test out things in gitbook.