>> I'd like to keep srfi.css small so as not to interfere with authors'
>> styling.  However, I'm happy to add some styling examples to
>> srfi-template.html.
>>
>> I've long had an item on my to-do list to curate good styling gathered
>> from across SRFIs and put it into the template so that people have
>> something good-looking and readable to start with.
>
> As someone who knows very little HTML from after the mid-1990s
> beginnings, would be very handy to have a canonical place where I can
> find for example more than one good  "SRFI style" table style, such as
> simple to complicated, vs. the first OK one from a search engine that
> probably does more than I need.
>
> Not sure they should be in srfi-template.html, vs. an separate file with
> concrete examples of their use in the body.  That would allow authors to
> view the results of using them, choose those they prefer, and add only
> those to their SRFIs.  That approach aligns with keeping srfi.css small
> and non-opinionated.

Last year's plans to convert all SRFI documents to a common HTML
structure have been on hold for most of this year since we're all so
busy. However, if this is still the goal, any template should be based
on that structure.

Would this be a good time to resume that work? We could pick a small
handful of semi-complex SRFIs and convert them fully. That ought to be a
good way to find flaws in any proposed structure.

Here's the WIP repo: https://github.com/srfi-explorations/srfi-conversion