[dogfooding] che-docs

[themr0c]

To make che-docs really usable on Eclipse Che, we need to add some tools and extensions.

• As a Eclipse Che user, from the IDE interface I want to build and serve the che-docs website

  • fix wrong redirection in serve che-docs task [dogfooding] wrong redirection in serve che-docs task #15865

• As a Eclipse Che user, from the IDE interface I want to create a new document using newdoc.

  • Integrate newdoc into the che-docs container. Add newdoc, test-adoc.sh and vale to the che-docs container che-docs#1058
  • Raise awareness about the usage of newdoc in the upstream README
  • make the usage of newdoc easier in Eclipse Che. Where and how? Enhance the devfile? Do we need to create a modular-docs VScode extension?

• As a Eclipse Che user, from the IDE interface I want to validate with test-adoc.sh the adoc file I am editing.

  • Integrate test-adoc.sh into the che-docs container. Add newdoc, test-adoc.sh and vale to the che-docs container che-docs#1058
  • Raise awareness about the usage of test-adoc.sh in the upstream README
  • make the usage of test-adoc.sh easier in Eclipse Che. Add a build task: in the devfile?

• As a Eclipse Che user, from the IDE interface I want to validate with vale the adoc file I am editing.

  • Add a very basic vale configuration enabling PlainLanguage checks. Vale config che-docs#1057
  • Integrate vale into the che-docs container. Add newdoc, test-adoc.sh and vale to the che-docs container che-docs#1058
  • Add the vale VSCode extension in the registry Add Vale vscode plugin to the plugin registry #15856
  • Make sure the Vale VSCode extension is working
  • Add the Vale VSCode extension in the devfile

[themr0c]

We have now a new che-docs container including newdoc, test-adoc.sh and vale. (And an updated jekyll and a newer version of ruby).

[themr0c]

This is done.