chore(other): add gitbook action

[Tirokk]

🍰 Pullrequest

Add gitbook action.

Issues

• fixes 💥 [DevOps] Setup GitBook with GitHub Pages for our Repo #6689

Todo

• try to use tab2, hints plugins to visualize the tab, hint MD annotation on the repository readmes
• file book.json:
  • set pluginsConfig.gtag.token?
• cleanup:
  • file .github/workflows/gitbook-action.yml
    • remove superfluid comments
    • set publish_branch again to master?
    • remove publish branch 6689-setup-gitbook-action
  • delete the test repos

[mahula]

The use of Gitbook and the Github Gitbook Action do not seem to fit our concern in the longer term.

• Gitbook is no longer actively developed or maintained with regard to dependencies. The latest version 3.2.3 is from 2017 (see https://github.com/GitbookIO/gitbook/commits/master)
• the Github Gitbook Action uses a 3-year-old Docker image of the author, which he also commented with a lack of further development regarding the NodeJS dependency (https://hub.docker.com/r/zanderzhao/gitbook-action)
• Gitbook issues have remained open for years due to execution problems with NodeJS >= 12.18.2. (see Gitbook build stopped to work in node 12.18.3 GitbookIO/gitbook-cli#110 and TypeError: cb.apply is not a function GitbookIO/gitbook-cli#115).

Since we already use Vuepress2, which comes from the vibrant Vue community and is actively developed, maintained and supported by the community, for various documentation purposes, it might be a concern for us to use this framework here as well in the long term and to exploit its potential for our needs.

The Markdown structure in the Vuepress repo might be a good orientation for our docs pages structure.

[mahula]

@Tirokk,

after #6836 is merged, can

• this PR be closed
• the doc.ocelot.social repo be deleted ?

[mahula]

The documentation automation hs been done with Vuepress2 in #6836.
So we're closing this.