fizzy
fizzy copied to clipboard
Create documentation
@chfast suggested we use sphinx/readthedocs, but we may as well just use markdown in the docs
directory.
Here's an idea on general layout:
- Introduction (what is fizzy, why, etc.)
- Build & usage
- Internals
- Internal representation (separate instruction and data stream/stack)
- "Optimisation techniques"
- etc..