Setup continous integration

[benjaminParisel]

Setup Github action to:

• build the site
• push it to github pages

when

• on push on bonita-doc content branch, trigger build here to push directly on the production
• Push on the right branch to put it on "production"

A poc has been done with 2 repositories to manage triggering a workflow stored in a repository from workflow located in another repository

• https://github.com/bonitasoft-labs/simulation-of-bonita-doc to simulate a documentation content repo
• https://github.com/bonitasoft-labs/bonita_doc to simulate the documentation site

For site generation and push to gh-pages in a GitHub workflow, we can have a look at https://github.com/process-analytics/bpmn-visualization-js/blob/v0.7.0/.github/workflows/generate-documentation.yml

Pending questions

Do we run a build when the master branch of this repo is updated probably yes to ensure new theme or antora playbook changes are used Should not been run on documentation changes (use exclude path)

Do we run a build when PR targeted master are created? In that case, we could build the site with the local profile and attach it as workflow artifacts. The resulting site could be then tested locally after having been downloaded In the future, we could deploy the generated site on a public free solution (netlify, vercel, heroku, ...)

[tbouffard]

1st implementation validated:

• push to gh-pages when master branch is updated
• run on demand
• BICI doc merge on master trigger a site generation and push to gh-pages