The goal of the website is to become a strong reference point that can be used to learn about opcodes one at a time of course, but also to be a resource you can always point to when writing formal documentation and referencing opcodes, for example in Stack Exchange questions and answers, library documentation, or blog posts. 

 Please consider the content alpha quality. But it's at the point where I feel like I've set up the feel/look enough to enable contributors to easily jump in and help on sections they know most about. If you like the idea, check out the repo and consider contributing! 

https://github.com/thunderbiscuit/opcode-explained