I am not very sure about the PRD acronym, but I tend to believe that it stands for "product documentation".  If not, still please read my point.

As a former technical writer, I would suggest we do it "the real Fedora way", because there is already a workflow [1] as well as a portal where all Fedora documentation is presented [2] to the end user.
In short, Fedora documentation uses a CI Git workflow, where the source files (written in AsciiDoc) reside in branches and are built upon a trigger by Antora framework and the result is immediately published.

The advantages of this approach are:

* AsciiDoc is similar to Markdown, so the basics can be learnt in a twist of time.
* AsciiDoc is also used at Red Hat, so we could probably cooperate with Red Hat documentation teams - after all, they will need such documentation after some time.
* Anybody can use whatever editor they like, some editors (Atom for example) have a live AsciiDoc preview, some do not, but it can be built anytime manually on your CLI.
* We do not need to look after anything, because the infrastructure is already set up and working.
* Fedora even has a dedicated documentation guy, Petr Bokoč, who is really knowledgeable and helpful, so I think he should be the one to speak about this, too. I am adding him to this thread.

Please, let's not waste time and resources on reinventing the wheel.

[1]: https://docs.fedoraproject.org/en-US/fedora-docs/contributing/
[2]: https://docs.fedoraproject.org/en-US/docs/


--

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka@redhat.com