I can implement all that extra stuff but I'd like to get the go-ahead
first. It's becoming a sizeable project so it's be nice to avoid wasted
work. At the moment I don't think any other workflow is viable compared
to this because the tools are written in Scheme, the GitHub integration
and Heroku web hosting are easy and free, and having the CI server be a
web server means we accidentally made an SRFI API with no extra effort.
I'd like to encourage any work that gets us better metadata extraction but doesn't change the visible content of existing SRFI documents (although it's fine to change the behind-the-scenes HTML, as you have been doing). In other words, I don't want to change anything that people have already agreed upon, i.e. the designs, the APIs, and the wording of the documentation. It looks like what you've been doing fits the bill.
I was hoping that you and Ciprian would come up with a Scheme format that would be good for encoding all that, but since the work you're doing can automatically generate whatever format we finally agree upon, there seems to be little risk in going ahead.
This sounds good. Just to be clear, though, would you mind laying out exactly what work you want to do in the official SRFI repos themselves?
Thanks, and thanks again for all your work on this.