When I said the documentation lacks a structure, this is what I meant... This isn't even all files in the "running mastodon" folder. How is anyone supposed to know where to start, what they need to read? I need to rework this into some kind of 1-2-3 story.
How about:
1. Installation
2. Configuration
3. Post-installation steps
4. Scaling up
5. Optional features
The old docs will still be on GitHub, so don't worry about that - I want to write new ones for the site. So how's this for structure?
Documentation site online with rough stubs for content. Didn't check how it looks on mobile yet
