https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

When you share on facebook the picture that shows up uses the "open graph" - it would be nice if using a STH image if this showed the the picture of the disk image, and had the games title.

The actual implementation of this sort of thing seems a bit of a pain though - basically serving a different page just to change output the right <og:image etc ...

http://stackoverflow.com/questions/16069501

See discussion in #233

This could be added to the manual, and/or example source code on disk.

I realize it would probably take a good deal of work, but it would be nice to have some documentation around the structure of the compiler and its execution flow. I would be interested in contributing to fix the bugs I've reported (big thanks for your prompt responses and fixes), but its difficult to understand the current setup without investing a great deal of energy.

The custom setup for documentation was fun, but Sphinx (developed for Python documentation) solves these problems in a simply, standardized way and can be combined with Read the Docs.

For an introduction, see http://www.ericholscher.com/blog/2016/jul/1/sphinx-and-rtd-for-writers/