Document the architecture and deployment steps (where possible)

[samtstern]

slaps roof this bad boy can fit so many moving parts in it.

We should create some basic documentation so that when we forget how it works, we can remember. It's like The Notebook and @abehaskins is Rachel McAdams.

[thatfiredev]

I believe this would also help more people from the community contribute to this project. Maybe they would be able to fix the other issues we have here, so this one should probably be prioritized.

[samtstern]

If you want to mess with the frontend, that part is pretty simple:

$ cd frontend
$ npm install
$ npm run dev

Then you'll have a local server that will automatically rebuild and refresh on any changes. That said I guess you won't have any data ... I wonder if giving the real data set public readability is a terrible idea.

Also while it hardly counts as documentation, the Makefile gives some idea of what's going on with the backend: https://github.com/firebase/firebaseopensource.com/blob/master/Makefile

[thatfiredev]

@samtstern This is actually helpful. Thanks!