Hm I do not get it, or I do not see the problem here, that is why we are improving papyrus, ok it does takes time because not many people working on that ...
I will try to explain again:
The whole idea is to move to a more modern approach, which we already started a year ago, that is why you helped to start fixing papyrus, remember ?
This is WIP and we still have to fix that more, but this the way we go and not only we, lost of other Projects from Google/Mozilla?Facebook and some others are going the same direction already.
We are in the process of moving away form one huge big docs repo, instead we are already started to fetch /docs from the repos, that is why I am telling ppl to write docs, according to our guidelines in /docs of the repo in your example that would be plone.scale/docs.
This is of course also not perfect, but has lots of advantages compared to one huge docs file/repo. One main reason is to be more flexible with versions.
So you work on a branch of plone.scale for Plone5.1 right ? This plip/fix is only for Plone 5.1 and not for lets say Plone 5.0.4.
You work on the branch of plone.scale for Plone 5.1 or you will merge it later into it right ?
Is that right to here ?
So when we fire up papyrus, which will be done by CI in the future, papyrus will build versions for Plone 5.0.4 and Plone 5.1 and since you change/plip/fix is hopefully merged into the plone.scale branch/repo for Plone 5.1 this change will be fetched by papyrus and build into the docs for Plone 5.1.
This change will not end up in docs for Plone 5.0.4
If you/we really prefer to have always a 'dev' build of the docs under docs.plone.org/dev [just an example name] we could do that, we even[should] add a huge banner with these are the docs of the dev version [also just an example].
Would that be helpful ?
We have also tools like mr.docs and currently under heavy wip, a new app called wtd-stack, with these you can build and check the docs locally or with ci in seconds or minutes, depends what you are testing/building
That is easy, because you can write docs in the same repo/branch where you write code, you do not have to bother with any other repo, one place where you do it all.
A no-brainer and easy doable.