Actually, there is no single hierarchy, just an artificial one created by my top page that makes it seem like one. Maybe there should be one or more real hiera

Actually, there is no single hierarchy, just an artificial one created by my top page that makes it seem like one. Maybe there should be one or more real hierarchies made as entrypoints to a large data set that can go in all directions without limit, in order to better meet reader expectations (but pls read on for more). With a possible exception of the very first page of the site, the things you are seeing as navigation, I have intended to be content first, and navigation second. (The document you found is an exception that I hope is temporary.) Almost all entries, things with bullets, are part of the content, even if it is also a link to more content directly related to that sentence. The situation might have been confused by the fact that at the entry level (~ top level, but really any point I consider an entry point in a way), some of the bullets really are navigational titles. My intent is that the size of the content (the number of pages and things I have to say about each thing, present and future) neither prevents reading the key points, nor prevents drilling down into more parts of interest. Again, to get the point across, and provide details, but to avoid "TL;DR" syndrome. So, maybe I should have a note at the top of many pages like "HOW TO READ CONTENT AT THIS SITE:" which links to a page that says "Every sentence is a sentence first and a link secondarily (or sometimes a title). So, to digest the information, read a page completely, then click on links of interest to read more about those statements." I tried to put something like that in a few places, but it describes it more in terms of skimming. So, there could be a need to better bridge the gap between typical expectations of web pages as documents, and the fact that I think of each page on the site as both navigation and content, almost like an app. There is so much content that to put it into a set of documents means choosing, somewhat arbitrarily, which content goes together, when in reality, it all goes together at every level, with an allowance for seemingly infinite amount of related content in all directions. (In fact, in the original system where these are stored, prior to being exported as html, each page and each entry on a page is an entity in an intended object model of reality including of thoughts, where each entity can have attributes including numbers & dates etc, code, and references to other data, trying to represent knowledge at an atomic level, considering documents as merely one type of expression of that knowledge. More at http://onemodel.org http://onemodel.org .) So, maybe I need to meet reader expectations by one or more of: - making (somehow auto-generating?) many entrypoints each with clear a hierarchy, - creating documents that are really data exports in outline form, to N levels. - finding a UX designer who understands the issues well and can suggest presentation techniques for this system, - or at least that I use the "HOW TO READ CONTENT AT THIS SITE" idea noted above. Ideas welcome. Thanks much for considering it to this point.