5 ms·
Oh I see how that was unclear. I don't mean using git as a database for user requests, but git as a back-end for collaborative applications. For example, in our
by hannes_paul 4y ago
Oh I see how that was unclear. I don't mean using git as a database for user requests, but git as a back-end for collaborative applications. For example, in our case, translators and devs have to collaborate to achieve localization. Normally translators would work in some isolated cloud application and then data pipelines between said application and the git repo are built. But why doesn't the translator facing app just build directly on git? Then editing the translation strings would happen on the git repo and there would be no synching between two sources of truth (git-repo and cloud solution)
- billconan 4y agoI think asking translators to use git is a hard sell.
- intelVISA 4y agoIts dirty core could be hidden behind some pastel colored buttons perhaps
- karmakaze 4y agoI think this is a pattern that does get used. The method I've seen is that the English language text is saved in files in particular directories with text keys. Translators add similar files with different text for the same keys and commit to the repo. Whether this is done manually or automated isn't a big deal. The app could even run the `git` commands and operate on the output of those commands and filesystem--there's nothing particularly hard to parse.