Map
A map is a document that lists other documents in the order to read them, each row with an optional one-line reason to follow it. The maps the charter names as home maps are the library's topics, drawn on its home page.

A library has no folder tree for a reader to browse; folders follow genres, not subjects. Maps are the structure instead. A document can sit on several maps, and a map can list other maps, so one library can have as many front doors as it needs.

What falls under a topic follows from the maps. Nothing on a document declares its topic.

How the maps nest, in this library

The home page is a map. The charter names four home maps under home.maps, and each lists its rows in reading order. Pick a topic to focus on it, as the Focus control in the top bar does: what falls under it stays lit, wherever it sits.

Focus
Home pagecontent/index.htmlThe map named home, under every topic. The shell draws a card for each home map, in the charter's order.
Using foliomaps/using-folio.html
  1. Getting startedguide
  2. folioproject · on two maps
  3. Why metadata comes firstentry
  4. One fact, one homeentry
  5. How corrections workentry
  6. As We May Thinkreading
  7. As We May Thinksource
  8. Q-1question · on two maps
Conceptsmaps/concepts.html
  1. Libraryconcept
  2. Genreconcept
  3. Mapconcept
  4. Skillconcept
  5. Packconcept
  6. Gateconcept
  7. Journalconcept
  8. Permanent recordconcept
Referencemaps/reference.html
  1. The folio modela spec, linked outside the library
  2. The genre formata spec, linked outside the library
  3. The checksa spec, linked outside the library
  4. The folio commanda spec, linked outside the library
  5. The pack formata spec, linked outside the library
  6. The skill formata spec, linked outside the library
  7. The shell's componentslinked outside the library
How folio is builtmaps/building-folio.html
  1. folioproject · on two maps
  2. Q-1question · on two maps
  3. check-timeprotocol
  4. R-1result
  5. R-2result

Using folio. The guide, the project, three entries, a source with its reading, and the open question. The project and the question are lit on How folio is built too: a document is on every map that lists it.

Concepts. The eight concepts. A concept is filed under no topic of its own: it also falls under every topic whose documents link it, so a focus on Using folio still reaches the concepts its entries use.

Reference. The specifications. They stay Markdown files outside the library, so this map links them by their addresses on GitHub, and they fall under no topic.

How folio is built. The lab records: the question, the protocol that tests it, and the two results. The project and the question are shared with Using folio.

The tree is drawn from this library's own maps. Rows that sit on two maps say so; with a topic in focus, they stay lit on both.

Maps, not folders

Folders follow genres

Every concept is under content/concepts/, every entry under content/entries/. That tells the engine what a file is. It tells a reader nothing about where to start on a subject.

Maps follow subjects

A map picks documents of any genre, puts them in order, and says why each is worth following from here. The same document can be on a map for newcomers and on a map for one project.

What one row holds

A link
To the document. The shell draws the link's text from the document's title, so a renamed document reads right on every map.
A reason, optional
One line on why to follow it from this map. Without one, the shell shows the document's description.
A place
Its order and its group heading, which the map keeps as written.
The trap: using tags as structure. Tags are facets for filtering. A reader arriving cold needs an order and a reason, and only a map gives them.

Related

The gate checks that every document except a journal entry is reachable from a map.

Who keeps them

The write skill puts each new document on a map in the same change. The organise skill moves, merges and splits maps with every link kept.