Prepare editor's draft generation/ rendering

[awoie]

We need a draft document to be generated / rendered automatically after each PR merge.

• hosted via gh-pages
• using ISO template and language to make it easier to transition the doc at some point (if the WG decides)
• do we need automation of the docx already? IMO, it will be needed when the draft is transitioned to ISO, but that can be done manually as well. Do we need a docx for feedback to ISO WG10 as well? In the past, we also shared the .html document/ online version and that was ok. If .html is fine, we might not need to automate this now.

[bhjelm]

Since the intent for the deliverable (of this WG) to be adopted as an ISO specification (see Issue #13), the proposal was to use an ISO format regardless of what (ISO) publication process the specification goes through. Having gone through the effort of converting OpenID Foundation specification into other SDO formats (ITU and ISO), the effort is significant (despite trying to use different template conversion tools).

If the WG decides to maintain two versions (for dual-publication) that's an option but adds additional work to maintain two formats of the same specification.

[awoie]

Since the intent for the deliverable (of this WG) to be adopted as an ISO specification (see Issue #13), the proposal was to use an ISO format regardless of what (ISO) publication process the specification goes through. Having gone through the effort of converting OpenID Foundation specification into other SDO formats (ITU and ISO), the effort is significant (despite trying to use different template conversion tools).

If the WG decides to maintain two versions (for dual-publication) that's an option but adds additional work to maintain two formats of the same specification.

I agree that it would be better to have only one version. The current PR implements an approach where the working group iterates on markdown following the ISO format and ISO directive. The result is a .html version of the editor's copy that is hosted via gh-pages. Additionally, the Github action produces a docx from the same source. This is an additional build artifact that can be distributed individually. See #11 .