With one (great!) writer doing all the awesome work on the Lubuntu Manual, as with all writing of this sort it should get a second set of eyes to make sure it flows well.
@isuzufan first off, good to have you here and thanks for the offer of help! The manual is held in a repository (rMANUAL) which is essentially composed of a bunch of text files in a reStructuredText format. Like other lightweight markup languages, it's highly readable except for some directives for building, which you can ignore. Every hour the public facing manual is rebuilt using the current code base. If you're familiar with using git, you can just submit pull requests using the cool little Phabricator tool Arcanist. If you need further explanation, don't hesitate to ask!
Thanks @wxl. The reStructuredText won't be hard for me to come up to speed on. However, I think I will need more guidance on how to access, work with, and then re-submit the text files. I'm a technical writer, but I usually work with other tools — I haven't worked in a developer environment to create documentation.
I looked at the repository and I see how the /source folder has all the Sphinx project files and then subfolders for chapters. I have no experience with Sphinx. What I would need help with is to set up the Sphinx project and understand how to retrieve, edit and resubmit files. I did see a link to a pycon video where a woman named Carol Willing talks about "Practical Sphinx"....I'll take a look. Any other resources you can suggest?
Hello gents, and possibly ladies. I've been reading through the documentation and have made some changes in github. Is it okay if I do it this way, or am I causing more work for you guys?