OK, if we generate the main page via cron job, all of that is doable without compromising on security and browser requirements. It's worth thinking about.If there's only a standards.scheme.org, under the current system that would be only one link on the front page. Would you keep it that way, or also have links to some of the individual standards on the front page?
Until we have enough material on the home page that there isn't room for all the detail, I would keep it there, too. Even after that, it might be good to do some sort of collapsible content on the home page that is automatically derived from standards.scheme.org.
As long as the desire to compartmentalize things doesn't result in a less useful, uglier home page, I'm happy to give in. Having the site survive for twenty years depends on us making the pages useful and not ugly.
That's also true. But keeping it maintainable tends to benefit from simplicity. The forces can be at odds and it's important to find a good balance.
Happily, web tech is flexible about how we do things: we can use
redirects, pre-generated statical files, different kinds of
inclusion by absolute or relative URL.
If we structure things around subdomains to make the organization easier to manage, Conway's Law says that the site itself will mirror that organizational structure, which I suppose is your goal.
Yes, deliberately making use of Conway's Law!
A major part of promulgating a set of customs over a long
timespan is simply remembering those customs. People have a hard
time remembering counterintuitive things even if they are written
down in some document. If everything is structured in a way that
reinforces the idea, the idea is easier to grasp and to keep in
mind.
It can be. I tend to have the opposite experience: I find most websites hard to navigate, and the more the authors obscure the URL structure of the site by freely mixing design elements, the harder it is to figure out the site as a user. URLs naturally form a hierarchical structure; websites whose linkage follows that URL structure tend to be the easiest to understand. That also lends itself naturally to so-called breadcrumb trail navigation, where the top of each page shows where you are in the hierarchy (e.g. Scheme.org -> Documentation -> SRFI -> 111).But it is often the case that that is at odds with building something great, so we have to be careful.