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.
For a few months I've been putting an hour or two every week on building a small encyclopedia of opcodes, mostly because I felt my opcode game was not strong enough to participate and reason clearly about all the new soft fork proposals.
There are 256 opcodes: I'm 80% done writing a small page for each of them. Today is the day I share this work publicly and invite people to come and join the fun.
Check out the website here: https://opcodeexplained.com/
Discussion
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!