Note: improvements based on feedback collected during the v0.2.2
release.
  - remove reference to a closed issue that is completed
  - manual release: add the "git tag" step
  - CRAN submission: better explain how to fill out the form

Setup everything to have a usable HTML documentation
The package Rd file is generated with `roxygen2`

Use a GitHub workflow to deploy
Update the DESCRIPTION file to mention the `gh-pages` URL
Update the Release workflow: update the release version in the doc site
as well (index.md)

#165)

Mention to update the `index.md` file that is now used to build the HTML generation.

Explicitly states that functions belong to the package and ensures that
there will be no ambiguity with a function of the same name from another
package.
Also remove extra trailing space in the source files producing the man
files.

Fix the paths configuration in the documentation GitHub workflows. They
didn't consider file changes, but only directory changes.

Add a new workflow to send message on twitter & discord, after a new
release is published.

⚠️⚠️ ⚠️  This is a breaking change. ⚠️⚠️⚠️ 

Users of the package must:
  - reinstall it from scratch
  - remove the old `bpmnVisualization` package
 - update usage of the package functions if they prefix them by the name of the package

…2.0 (#176)

Update the maintainers documentation to remind writers to notify users through the release notes. In this case, the new version of the package will be install using GitHub.