Automating Reference Documentation publication

[NikolajBjorner]

Currently the reference documentation is built on releases and available as a zip file from the release hive.

https://github.com/Z3Prover/z3/releases/download/z3-4.9.1/z3doc.zip

Then I manually download this and unzip the contents into z3prover.github.io/api/html
It is a repository under https://github.com/z3prover
Commit and push

The process for uploading artifacts should be reasonably similar for releases.
Even a self-contained GitHub action that builds documentation by itself and pushes to the right place (could be microsoft.github.io/z3guide if this is better) would be great and perhaps easier to maintain than complicating the release.yml Azure pipeline.

[NikolajBjorner]

Parameters.md are now generated as part of documentation build.
From there they are currently manually copied to z3prover.github.io and to github.com/z3prover/z3 landing directory.

[pelikhan]

@NikolajBjorner can you walk me through this process? maybe i can help automating this

[NikolajBjorner]

Can it be copied from z3doc.zip asset from

[NikolajBjorner]

I other words create an action that triggers on relaese to copy over parameters.md, and optionally update z3prover.github.io