#musicbrainz-picard-development

I'm still looking at how the new repo structure for the Picard documentation should look, and my current sticking point is how to handle translations and the setup on Weblate. It appears that the master branch and 2.x branch are handled separately in the Picard repo. I think this will also make sense for the Picard documentation, but I'm not sure what will be required to change the setup in Weblate (or

whether I have the access to make the changes). Am I correct in assuming that each version branch (such as 2.x) would be a different component in the same Weblate project?

Also, we're currently hosting the Picard Documentation as a gh-pages branch in the repository. Are there any concerns if we consider switching this to be hosted on ReadTheDocs instead? It will mean some major changes to the document management and publication workflow, but I think it may end up being easier to maintain in the long run.

I'm not sure about making two versions translatable. With the amount of separate components in weblate managing the translations is already quite involved. I think it would be ok to make only the latest version translatable

Regarding readthedocs I have no strong opinion. I know you tried both originally, but I can't remember if there was a specific reason for choosing GitHub, or if it was just that both worked well

But since MB uses rtd for other things as well (LB docs mainly I think) it would be fine to host the Picard docs there as well. It would even reduce the dependency on GitHub a bit

Back when you initially did the docs project I also did a test deploy on rtd and found it to work well