link from readme

[crimsonsunset]

Checklist for Pull Requests

🚨Please review the guidelines for contributing to this repository.

• [ ] Make sure your branch matches the naming conventions. (Something like: AC-152). Don't request your master!
• [ ] Your branch should only contain changes relevant to the ticket it is named after.
• [ ] Make sure you are making a pull request against the dev branch (left side). Also you should start your branch off our dev.
• [ ] Check your code additions will fail neither code linting checks nor e2e test (this will be tested automatically when you open your PR).

Description

Please describe anything in your pull request that isn't immediately understandable from the ticket description.

Thank you! 😎

[crimsonsunset]

the only actual changes in this PR are the links from readme out to all the new documentation. I just threw a prettier in there because it has been a while since we did so. As part of this PR, if someone wanted to check the actual new documentation that's been created that would be 👍

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
1.4% Duplication