Codebase diagram

[Mecharyry]

Problem

New developers that want to work on no-player may find the codebase hard to navigate / not understand fully how different aspects join together.

Potential Solution

Create a high-level diagram for no-player to give an idea of the key links that operate together to make no-player work. We could use https://leanpub.com/visualising-software-architecture or some alternative. I have not looked into this in great detail but I think it would be worthwhile.

Impact

Simplify the onboarding process of new developers.