All the pages that are assumed by the software should not be site-specific anyway. They should be stored someplace centrally, where the help of each site can link to. Codidact could still retain control over editing those pages, but how/when they are presented within the broader overall help can be edited per site. There should probably be a general high level Codidact help page that references all that stuff. This would make it easy for the help of particular sites to reference, while not having to duplicate it all. This is where information goes that is common to all sites, or otherwise doesn't apply specifically to individual sites. For example, how the post editor works is common to all sites. The political details of the Codidact organization and the software is not relevant to any individual site.

I'd like to find a way to protect the general content (that the software depends on for links) while still allowing local extension. For example, the formatting page is linked from the post editor. A few communities use MathJax or code syntax highlighting, and it would be great to be able to link to those additional topics from the formatting page on those communities but not all of them. (Why bother cooks with information about MathJax?) That much could still be baked in, but what if EE wants to add something about how you expect diagrams to be formatted? Ideally you'd be able to add that in. I hope we can come up with some scheme that enables that while still protecting the stuff that should be invariant.

In that case those links used directly by the software should be settable. Hard-coding constants into software is bad practice anyway. If links, like those to context-sensitive help about formatting posts, are settable per site, then they can be pointed to site-specific help pages, which can refer to the more general help if they want to.