Feature/documentation pages

[anhcq151]

close #16
Github pages setting should use doc-pages-uat as source branch and /root folder to build page.
My workflow is:

• Doc writer write new doc page in asciidoc format, save into docs folder then push to branch feature/documentation-pages
• Github action will convert all .adoc file to .html file and push to doc-pages-uat branch

[zero88]

@anhcq151 You can use one of these tools due to Asciidoc python is legacy:
https://docs.asciidoctor.org/maven-tools/latest/
https://asciidoctor.github.io/asciidoctor-gradle-plugin/development-3.x/user-guide/
https://docs.asciidoctor.org/asciidoctor.js/latest/ (js version)

I prefer maven or gradle.

[anhcq151]

@anhcq151 You can use one of these tools due to Asciidoc python is legacy:
https://docs.asciidoctor.org/maven-tools/latest/
https://asciidoctor.github.io/asciidoctor-gradle-plugin/development-3.x/user-guide/
https://docs.asciidoctor.org/asciidoctor.js/latest/ (js version)

I prefer maven or gradle.

I've updated code using mvn

[zero88]

Once you finish, remove all document that you already migrated

[zero88]

Use maven-site-plugin will create a typical maven document, it does not meet our brand style.

It is better if you can follow this example project to create simple HTML5 site, then add styling later (in another ticket)

Check it out and run in local to see how it works, also review its document structure.

Current structure is not good. Should split document folder as functional instead of technical name (ansible, python), also make a boundary between user guide an development document