Paul Roeland

I find the 'readability' warnings to be less than useful, they're all "try to keep the GobblediGook (x.y) Index below (z). Usually meaning your text is a bit convoluted, but...

Since I haven't **quite** mastered the art of "adding a few extra products to the testing fixture in order to do screenshots", having a manual screenshot is much better than...

I'm not 100% on how to do it through the GitHub web interface. When cloning locally, it's a simple "git add mypicture.png". As for folders: just put in the same...

ah, there is that suspicious 'new file' button on the webinterface; so through the web should be: - create branch - hit the "new file" button on the correct directory...

I'm sorry; that is something we will have to improve then. (also for safety; you deleted the whole 4.3 branch in the process. Easily enough to restore, but that means...

ah, found them already. https://github.com/plone/documentation/commit/aeaed22b874ace77f3c8bb529ff455a3226bb6d8 and https://github.com/plone/documentation/commit/e3eda04ab10eab3d881c1e9e661adb37ea41816b, so to see. I'll work from there

no problem, it shows we need better documentation ;-) I'll have to find a computer where I can install github-desktop, then make some screenshots using that.

no, not yet. The documentation pulls in lots of stuff from the /src directory, and uses extra modules. Will have to work with tisto to see how to best handle...

Consolidating is good. The 5.2 docs pull in coredev from the coredev-5.2 branch, so that should be left alone. In the 6 branch we can move to docs

@stevepiercy that's also what we do. We have a playbook that - stops what's running on port 80 (nginx in our case) - runs renew - restarts nginx a bit...