[Docs 02] Auto dev-docs & more

[MyDrift-user]

Pull Request

Documentation update

Type of Change

• Documentation update

Description

• autocreate documentation for every tweak/feature with description, reg keys, services, tasks, features, invokscripts, undoscripts and nested referenced functions.

• Create table of content for docs page linking to every generated file.

• archive unused autocreated documentation.

• redo navigation on docs site

• moves code of conduct & contributing to root directory to adhear to github standards and be recognized, but referenced in docs to still have them in the docs without having duplicate files.

  • helps Missing Community Standards #2504

• add hyperlink to docs page for tweaks & features

• dependency for [Refactoring UI Code] WIP: Inline UI Definition instead of xaml compilation #2465, so not only the applications but also anything else gets it's "?" hyperlink to the docs page.
  
  

• Support of the "link" member in the json files for toggles, buttons & more will be extended in [Refactoring UI Code] WIP: Inline UI Definition instead of xaml compilation #2465

• CI/CD support for this new script will be added in [CI/CD] WIP: Re-use Workflows to Ensure GitHub Pages is built after every pre-release - Cleanup Workflow Naming Inconsistency - Remove 'release.yaml' workflow #2471

There are currently 2 places per autocreated site to write custom descriptions into, which won't get overwritten by updating the files. They are marked by markdown comments in the file.

• One on the top below the code preview
• one at the bottom just above the link to the referenced file the source was taken from.

See the auto generated documentation on following site:

• https://mydrift-user.github.io/winutil/
• https://mydrift-user.github.io/winutil/devdocs

Testing

• table of content page is created & updated sucessfully
• documentation files are created without and issues on my side
• linking to and from docs work
• links are correctly added into json files

Impact

• big impact for people who want to know how it works, but don't want to search through the .json files in the repo.

Checklist

• My code adheres to the coding and style guidelines of the project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no errors/warnings/merge conflicts.

[MyDrift-user]

I did get the Changelog link to the docs for the about section to work, but undid it because at the moment the github release notes and the changelog notes are not that diffrent. GitHub Releases Changelog is at the moment still superior, so it will stay that way for now.

[ChrisTitusTech]

Looks great, thanks for your work on this.