I had mentioned the docs.microsoft.com effort and I happened to look more closely to how much it has been documented and the production approach performed in the open (and partly because a friend's team worked on it).
This page is remarkable <https://docs.microsoft.com/en-us/contribute/> This is all about documentation on the web (although I see a PDF button on the bottom of many of these pages). What is remarkable is how much is introduced to allow non-technical users to contribute to the docs via the Quick Edits provisions. And then there is the GitHub origin of the authored forms for those who want to go deeper. And all of the tooling to accomplish that is documented in setting up to work locally using freely-available fixtures. This is far off from a model that revolves around editing of ODT documents or other ODF versions as implemented with Apache OpenOffice. On the other hand, it would be interesting to see how some means of memorializing and onboarding and sustaining of the current AOO effort might find inspiration In the substantial effort to have docs.microsoft.com produced in the open. Cheers, - Dennis -----Original Message----- From: Dennis Hamilton Sent: Monday, February 15, 2021 11:27 To: 'doc@openoffice.apache.org' <doc@openoffice.apache.org> Subject: Using GitHub as a platform for creating documentation and publications Something that might be helpful to consider is the fact that Microsoft is moving all of its on-line developer documentation (that is, for developers and IT administrators as users) to GitHub: <https://github.com/MicrosoftDocs>. This is a gigantic project. Although MicrosoftDocs usage is specific to Microsoft and there seems to be some custom tooling, there is also some attention to on-ramping: <https://github.com/MicrosoftDocs/microsoft-365-community/wiki/Getting-Started>. (This takes advantage of GitHub having wikis available for every project.) Note that the MicrosoftDocs customized use of GitHub is for production of on-line documentation. I am not urging their model, just pointing that there may be information that is adaptable for Apache/openoffice-docs on GitHub. I have been thinking of Document Engineering as a methodology around production of digital publications, web content, etc. I've started a project on that subject at <https://github.com/orcmid/docEng>. This will focus on writing-in-the-open on collaborative document-engineering with GitHub as the platform. This is completely separate from the openoffice-docs efforts and I will say no more about it here. It is not about producing AOO docs, but some of the tutorial materials may be helpful to those who want to author, edit, or review openoffice-docs contributions. - Dennis [orcmid] [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org For additional commands, e-mail: doc-h...@openoffice.apache.org
