Hijacking Repo - Githubissues

[ ] Decide if we want to split this into separate issues for the project view or keep it like this.
[ ] Going through old issues and updating/moving/deleting as suitable.
[ ] Having a look at the old project and deciding if it is still relevant.
[ ] Moving the ToDo-list from the pad into relevant issues.
[ ] Setting up an issue for walkthrough documentation (how to Codi, Slack, GitHub etc.)
[ ] Setting up an issue for more philosophical documentation (Do-ocracy, the meaning of life, etc.)
[ ] Organising a structure (on the Wiki?) for permanent documentation.
[ ] Having a look at the Teams and Volunteering pages to see if they need updating based on the above-mentioned changes.
[ ] Renaming the repo as "Community" is somewhat vague? (There are other "non-tech" repos, so perhaps that term would be too all-inclusive.

Trustroots / community