Lassi Kortela <xxxxxx@lassi.io> writes:

| I just timed editing two SRFIs from scratch using the tool. SRFI
41 took 12 minutes and SRFI 72 (a large one) took 20 minutes. If 3
people each edited on average 2 SRFIs per day, we'd have the
entire back catalogue done in a month!

This is useful information.

| * Would be nice if somebody adds that HTML metadata to new
SRFIs. As demonstrated, this shouldn't take more than half an hour
even for the most complex SRFIs.

I'm happy to put this in the template, but I won't require it of
authors.  I'll just encourage it, assuming that we decide to use
this approach.

| * Though requirements on HTML are lenient, what would really
help is to mandate that all tags have closing tags. Unbalanced or
missing tags have really been the only detriment to
machine-parsing that I've encountered. There are "lenient linters"
that check only this, e.g. https://www.jwz.org/hacks/validate.pl

That should be easy to do after the fact.  However, in
HTML5, certain elements, e.g. <img>, <input>, <br>, <hr>, and
<meta>, are not allowed to have closing elements:

  https://dev.w3.org/html5/html-author/#void

In those cases, we'll have to use self-closing tags.

| I guess it would be best to store the S-expression files in the
same git repo where we have the SRFI itself.
...

Yes, that's what I was thinking, too.