docs: Prepare docs for OSS release [WIP]

[s-gbz]

Closes #75

POTENTIALLY BREAKING CHANGE! Please check out this branch and try commiting a faulty commit message ("asdf" or, more accurately "featX") <- You should receive a reasonable error prompt á la

git commit -m "fas"
⧗   input: fas
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

husky - commit-msg hook exited with code 1 (error)

Valid commits would naturally cause no trouble

Reviewer's task:

• [x] I didn't see no code smells
• [x] The live preview works as expected -> no regressions found

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
screenario	✅ Ready (Inspect)	Visit Preview	Sep 4, 2022 at 9:30AM (UTC)

[s-gbz]

@all-contributors please add @s-gbz for infrastructure, code and design

[allcontributors[bot]]

@s-gbz

I've put up a pull request to add @s-gbz! :tada:

[s-gbz]

@all-contributors please add @liam-k for design, code and infrastructure

[allcontributors[bot]]

@s-gbz

I've put up a pull request to add @liam-k! :tada:

[liam-k]

Alright, we got Readme & Contributions pages now. Let me know if there’s anything you’d like to add (or just add it). I commented out the section about testing for now because I’m not sure how much testing you actually implemented.