Refactoring of the user documentation

[dcoraboeuf]

• Quickstart
• SaaS access
• Installation
• Setup
• Authentication
• Concepts
• Authorizations
• License management (pro only)
• Feeding information
• Integrations
• Using the UI
• Features (by categories)
• Administration
• GraphQL reference
• REST reference
• DSL reference
• Metrics
• Developing Ontrack
• Architecture
• Extending and extension points

Misc:

• Quick start links from the README
• Publish a version 4 in Docker Hub
• Make the JDBC based security a default

[SansGuidon]

Dont hesitate to add me as reviewer :-)

[dcoraboeuf]

I will :) There is already a branch associated with this ticket.

…

On Sun, 22 Nov 2020, 15:51 Morgan, ***@***.***> wrote: Dont hesitate to add me as reviewer :-) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJGVNCOMQRI3O6YQKDQZYTSREQQRANCNFSM4T6MOQAA> .

[dcoraboeuf]

@MorganGeek , if you're interested in reviewing the documentation (and in contributing), you can get the draft in the feature/822-documentation branch. You can build the doc locally by running:

./gradlew -Pdocumentation asciidoctor

Careful: starting from v4, Ontrack wants a JDK 11. I personally install it using SDKMan.

Upon generation, the doc is available at ontrack-docs/build/docs/asciidoc/index.html

It's also possible to generate the PDF using asciidoctorPdf.

[dcoraboeuf]

In order to have a more streamlined delivery, I'll merge the new documentation skeleton into the existing documentation, moving the old one in the appendixes for now. This way, the old & new documentation will live together while I keep moving the old doc into the new one.