I'm still thinking about this, but more leaning towards treating Scaladoc comment as part of code. We should just cut a release and let it go. Any improvement should just wait till 0.13.6. There are several benefits for this:
- Documentation maintenance of 0.13.5 doesn't cut into the development time of 0.13.6.
- Having the clear deadline should force us to review API docs as part of milestone process.
- When we ship zipped version of the API, what we shipped on the release date is the same thing we show on the website.

I only deleted the Sphnix related code. site.settings is just commented out.