Valentin Gagarin <valentin@gagarin.work> writes:

>> I'd prefer to handle the redirects in nginx config if that's okay with
>> you, so it's a proper server-side redirect.
>
> The plugin generates a `_site/redirects.json` file that you can already 
> feed to the web server.  It's already enough to have to keep track of 
> those redirects manually at all.  You shouldn't have another layer of 
> manual work on top.

Alright, we can work with that.  I'm mildly concerned that
the plugin hasn't been released in the last 6 years, but maybe it's just
done I guess…

>> Are we adopting FileCopyrightText then License-Identifier as the
>> official style, then?  I'll do it across the board if so — if it's
>> important enough to rearrange, we should be doing it consistently.
>
> I think we should, but we could just do it lazily, when we touch those 
> parts.  But if that produces too much diff noise, feel free not to pick 
> the reordering and do a separate bulk change.

Alright, doing it lazily sounds fine as long as it's consistent.  If it
annoys me sufficiently I'll do a bulk change.

>> 
>>> -    <li><a href="contributing.html">Contributing to Spectrum</a>
>>> +    <li><a href="doc/contributing/index.html">Contributing to Spectrum</a>
>> 
>> doc/contributing is nicer, no?
>
> I don't have an opinion there, but if you want that, it should be 
> `doc/contributing/` to avoid the permanent redirect on first access.

Makes sense to me.