Add documentation on tooling for working with Asciidocs

[j-medland]

I think I can contribute some notes that would be helpful for folks wanting to contribute to the documentation including

• Text editor and extensions
• Steps to build and preview locally
• Anything else that occurs when I write the notes out

[unifab]

@OlivierJourdan and I added the toolchain I am using as well as how to render the Antora website locally.
https://github.com/LabVIEWCommunityTraining/cti-documentation?tab=readme-ov-file#rendering-pages-on-your-computer

Perhaps adding your notes to that section and other relevant README sections would be great!

Thanks,
Fab

[j-medland]

I appreciate that this is a bit meta but should we add an additional set of Antora-built pages on "Contributing Course Material"?

• Why we like Asciidoc and Antora
• Getting setup for local development with InteliJ or VSCode
• Building the Pages Locally (Installing Node JS, Installing Deps, ignoring scary looking warnings, Building and Opening Site)
• Asciidoc Cheat Sheet and Style Guide

It can also contain advice for folks new to Asciidoc or give advice or tips if you want to convert any content across.

Thoughts?

[OlivierJourdan]

I think you nailed all the main points we should address.
Concerning the order of importance, I would start with "Why we like…" and then the "Asciidoc Cheat Sheet and Style Guide", focusing on what we think helps write content for the courses.
The other 2 points will interest the leading writers of courses. They are essential but may not interest everyone (at least not the contributors who will fix issues or translate directly in GitHub.

[OlivierJourdan]

I didn't say it, but I'd be happy to help if you need it.

[OlivierJourdan]

@j-medland, @unifab I moved the issue to this project because this is the project that now handles the generic information about CTI.