Tip
The docs as explained here are used in multiple projects, but documented only once for better maintenance. When applying this to other projects, remember that some things such as the name, repository, or paths are a bit different.
Contribute to Documentation
First of all: Thank you ππ½ for considering to contribute to the documentation π. We really appreciate it.
These are the things you can do, in order of complexity. You should really start with the first one, and only move on if you're comfortable with it.
- Just get the docs and view locally
- Improve existing content
- Add new content, link around and add tables of Contents
- Create/improve docs to the C# source-code
- Create/improve docs to the JavaScript source-code
- Create/improve the build process
Level 1: Get the Docs and View Locally
Download the docs to your PC and figure out the VS-Code setup, so you can work locally and preview the result.
β‘οΈ Setup & Preview Docs Locally using VS-CodeRun the docs-build to see if everything works.
β‘οΈ Build the Documentation
Level 2: Improve Existing Content
Content is written using Markdown. This is a common format used for Wikipedia, GitHub and many other places.
- Enable the preview in VS-Code to see your changes live.
β‘οΈ Enable Preview in VS-Code - Remember to re-run the docs-build to see if everything works.
β‘οΈ Build the Documentation
Once you've grown comfortable with Basic Markdown, you can also learn about Images, Lightboxes and then move on to Galleries, flowcharts and more.
Level 3: Create New Pages and TOCs
After graduating from Level 2, you can start creating new content and linking it together. This includes things like:
- Create new markdown pages
*.md
- Link to them from other pages
- Create and modify tables of Contents
- Learn about Permalinks (UIDs) to ensure links don't break
Level 4: Docs to C# Source-Code
Here things can get a bit more challenging, which is why we saved this for Level 4. Basically we'll use the XML-comments in the C# code to generate documentation.
Read about documenting source code and namespaces
Then Build Docs and Code.
As you get better, we suggest reading the Technical Implementation of the Docs to understand how everything works.
Level 5 & 6
...not explained in detail, but you'll find everything you need in the TOC to the left.
Note about Copyright
All docs are licensed as CC-BY. By contributing you agree that your work can be used in this way.
Questions
For further discussions, feedback, or questions, head over to GitHub Discussions or GitHub Issues.