Docs: document overview/use cases
What
Document how to and why to add overview and use cases to every major feature.
Why
It's important to provide an overview and a couple of use cases to every new feature, as we have done for most of the current ones. We need to document how this should be done:
- Overview: pretty much self-explaining, provide an overview of the feature. Describe what is it, what does it do, why is it important/cool/nice-to-have, what problem does it solve, and what you can do with this feature that you couldn't do before.
- Use cases: provide at least two, ideally three, use cases for every major feature: what can you do with it? Use cases are examples of how this thing could be used in real life.
Where
Into writing documentation I think