Documentation

[SeeratSek]

We don't have docs. we need them.

Possible structure:

• Architecture:
• Design Decisions:
  ** Websockets: Bi-directional communication. Important because the server runs the game and needs to send messages to the client without being requested.
  Persistent connection. Normal HTTP requests/responses are not suitable because of the reason above, but also because there is some overhead with opening and closing connections over and over again.
  Really easy to implement. We wanted a fast prototype and WebSockets are already native to browsers. Simpler and more supported than a raw TCP socket.
  ** Go
  ** ... other
• How others can contribute

Possibly can create a medium post to rationalize design decisions in depth + share problems we faced + future goals

[bobheadxi]

Let me know if you guys get a medium post up, I can add it to the Launch Pad publication 📚