@heroiclands/package-build 23.13.0 → 24.0.1

package/docs/reference/note-types.md

@@ -463,11 +463,12 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.names`            | a language's name lists                                                                                                                      | How this language's speakers are named, for `package-build npc new`: `pattern` builds a name from placeholders such as "{given} {clan}" and literal text, `given` maps a gender to a list of given names, `female` and `male` required, and every other key is a list of names a placeholder of the same name draws from. A language skill note only. See [name lists](format-details.md#name-lists). |
 | `data.family`           | an Address                                                                                                                                   | The parent language, as a language skill note: this language reads the parent's words, and its parents' in turn, as its own. A language skill note only. See [a language's words](format-details.md#a-languages-words).                                                                                                                                                                               |
 | `data.abbreviation`     | a string, such as `Prov.`                                                                                                                    | The tag a dictionary prints for the language, beside an entry's class and in an etymology, as `Prov.`; the language's full name where unstated. A language skill note only. See [a language's words](format-details.md#a-languages-words).                                                                                                                                                            |
+| `data.core`             | `true` or `false`                                                                                                                            | Whether the language must cover the core vocabulary: `true` lists it in the `package-build core` report. A language skill note only. See [the core vocabulary](format-details.md#the-core-vocabulary).                                                                                                                                                                                                |
 | `data.classModifiers`   | list of word class modifiers                                                                                                                 | The class modifiers the language uses, from the master word classes. A word's class may carry only these. Empty when unstated. A language skill note only.                                                                                                                                                                                                                                            |
 | `data.fields`           | list of `{ name, holds }`                                                                                                                    | The fields the language's words are grouped under. A language skill note only.                                                                                                                                                                                                                                                                                                                        |
 | `data.words`            | list of `{ form, class, field, gloss, … }`                                                                                                   | The words this language states, one map each, in authored order; its automatic dictionary sorts them alphabetically. A language skill note only. See [a language's words](format-details.md#a-languages-words).                                                                                                                                                                                       |
 | `data.affixes`          | list of `{ form, gloss, attaches?, examples? }`                                                                                              | The affixes a word's `built` pieces may name, each with its gloss. A language skill note only.                                                                                                                                                                                                                                                                                                        |
-| `data.grammar`          | a map — `{ plural?, verbs?, agreement?, participles? }`                                                                                      | Optional noun plurals, one verb pattern, agreement and participles, for dictionary presentation and the mapped-run word check. Only the shape of supplied keys is checked; no word must follow or state a rule. A language skill note only.                                                                                                                                                           |
+| `data.grammar`          | a map — `{ plural?, verbs?, agreement?, participles?, native? }`                                                                             | Optional noun plurals, one verb pattern, agreement, participles and the endings' logographic writings, for dictionary presentation, the mapped-run word check and logographic maps. Only the shape of supplied keys is checked; no word must follow or state a rule. A language skill note only.                                                                                                      |
 | `data.tongues`          | list of `{ tag, meaning, language? }`                                                                                                        | The tags a register row's `tongue` may name, each with what it means. A language skill note only.                                                                                                                                                                                                                                                                                                     |
 | `data.register`         | list of `{ name, tongue?, kind?, built?, gloss?, why? }`                                                                                     | Every name the setting gives in the language's reach, with its tongue and pieces; the notes carrying each name are derived. A language skill note only.                                                                                                                                                                                                                                               |
 | `data.retired`          | list of `{ form, instead?, why }`                                                                                                            | The forms the setting does not write, and why. A language skill note only.                                                                                                                                                                                                                                                                                                                            |
@@ -481,6 +482,8 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.older`            | list of `{ form, gloss?, layer? }`                                                                                                           | The words and names older than the language's rules, which no sound or name rule holds. A language skill note only.                                                                                                                                                                                                                                                                                   |
 | `data.negation`         | a map — `{ particle, mutation? }`                                                                                                            | How a verb is negated. A language skill note only.                                                                                                                                                                                                                                                                                                                                                    |
 | `data.naming`           | a map — `{ shapes?, edges?, draws?, heldFrom?, nearName? }`                                                                                  | The shapes, edges and sources the language's names keep beyond its words' rules. A language skill note only.                                                                                                                                                                                                                                                                                          |
+| `data.emphasis`         | `words`, `rubric` or `overline`                                                                                                              | How the language marks a stressed word, over its script's `emphasis`: `rubric` or `overline` sets `*…*` and `**…**` so in a run of the language, and `words` marks it with a word, so either is a finding. Only a skill of `subType: language` states it.                                                                                                                                             |
+| `data.script`           | a map — `{ fonts, emphasis, strongEmphasis? }`                                                                                               | A script note's faces and how it marks emphasis. Only a skill of `subType: script` states it.                                                                                                                                                                                                                                                                                                         |
 
 **Inner keys** — a key a field's value does not declare is an error at its own line and column.
 
@@ -491,12 +494,13 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.fields[].name`                      | a string                                                                                                  | yes      | The field's name, which a word's `field` names.                                                                                                                                                                                                                                                                                          |
 | `data.fields[].holds`                     | a string                                                                                                  | yes      | What the field holds.                                                                                                                                                                                                                                                                                                                    |
 | `data.words[].form`                       | the word as cited, bare                                                                                   | yes      | The word as cited, with no backticks.                                                                                                                                                                                                                                                                                                    |
-| `data.words[].variants`                   | a list of forms                                                                                           | no       | The word's other forms, such as a long form beside a short one; a marked use of one cites the word.                                                                                                                                                                                                                                      |
+| `data.words[].variants`                   | a list of forms                                                                                           | no       | The word's other forms, such as a long form beside a short one; a marked use of one cites the word, and a mapped run accepts it and the forms the language's rules derive from it.                                                                                                                                                       |
 | `data.words[].name_sort`                  | a string                                                                                                  | no       | The sort key; the form when unstated.                                                                                                                                                                                                                                                                                                    |
 | `data.words[].class`                      | a word class, base first, such as `n I f`                                                                 | yes      | A class from the master word classes: a base, then the modifiers the language declares in `classModifiers`.                                                                                                                                                                                                                              |
 | `data.words[].plural`                     | a string                                                                                                  | no       | The noun's explicit plural, where it differs from the language's optional plural rule. A dictionary uses this form before the rule; no rule agreement is checked.                                                                                                                                                                        |
 | `data.words[].field`                      | one of the language's `fields` names                                                                      | yes      | The field tag beside the dictionary entry, named in the language's `fields`.                                                                                                                                                                                                                                                             |
 | `data.words[].gloss`                      | a string, or a list of senses                                                                             | yes      | The meaning, in brief; a list states one sense per entry, which a dictionary numbers.                                                                                                                                                                                                                                                    |
+| `data.words[].concept`                    | a core concept's id, or a list of them                                                                    | no       | The core concepts the word serves, each an `id` of a `data.concepts` list. The core report counts the word toward them.                                                                                                                                                                                                                  |
 | `data.words[].source`                     | a map — `{ kind, language?, form? }`                                                                      | no       | Where the word comes from.                                                                                                                                                                                                                                                                                                               |
 | `data.words[].source.kind`                | one of inherited, borrowed, kept, worn, coined, substrate, island                                         | yes      | How the word came into the tongue.                                                                                                                                                                                                                                                                                                       |
 | `data.words[].source.language`            | a language skill Address                                                                                  | no       | The tongue the word was borrowed from; required for `borrowed`.                                                                                                                                                                                                                                                                          |
@@ -507,10 +511,10 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.words[].tones`                      | a string                                                                                                  | no       | A tone pattern, such as `LHL`.                                                                                                                                                                                                                                                                                                           |
 | `data.words[].root`                       | a string                                                                                                  | no       | A consonantal skeleton, such as `d-l-k`.                                                                                                                                                                                                                                                                                                 |
 | `data.words[].frame`                      | a frame of the language's `sounds.frames`                                                                 | no       | The frame a root is set in, named in the language's `sounds.frames`.                                                                                                                                                                                                                                                                     |
-| `data.words[].native`                     | a list of `{ map, font?, text }`                                                                          | no       | The word's native form under a map, stated only where the map's rows spell it differently. Its derived forms are spelled by the rows.                                                                                                                                                                                                    |
+| `data.words[].native`                     | a list of `{ map, font?, text }`                                                                          | no       | The word's native form under a map. Under a map that spells by its rows it is stated only where the rows spell the word differently, and the word's derived forms are spelled by the rows; under a logographic map it is the word's writing, which its derived forms and the words built on it are written from.                         |
 | `data.words[].native[].map`               | a mapping note's `data.map.name`                                                                          | yes      | The map the native form is written for.                                                                                                                                                                                                                                                                                                  |
 | `data.words[].native[].font`              | a face the map lists                                                                                      | no       | The one face the native form is for; unstated, it is for every face the map lists, and a form stated for a face wins over it there.                                                                                                                                                                                                      |
-| `data.words[].native[].text`              | the word in the script, as the map's characters                                                           | yes      | The word as the script writes it, where the map's rows would write it otherwise.                                                                                                                                                                                                                                                         |
+| `data.words[].native[].text`              | the word in the script, as the map's characters                                                           | yes      | The word as the script writes it, where the map's rows would write it otherwise, or as a logographic map writes it.                                                                                                                                                                                                                      |
 | `data.affixes[].form`                     | the affix as written, such as `-rith`                                                                     | no       | The affix as a word's `built` names it; absent on a zero affix.                                                                                                                                                                                                                                                                          |
 | `data.affixes[].zero`                     | `true`                                                                                                    | no       | The affix is written as nothing, such as a case with no ending; it states no `form`, prints as `∅`, and no `built` piece names it.                                                                                                                                                                                                       |
 | `data.affixes[].kind`                     | one of case, derivation, tense, aspect, mood, voice, name, lineage                                        | no       | What the affix makes.                                                                                                                                                                                                                                                                                                                    |
@@ -525,6 +529,10 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.affixes[].examples`                 | a list of strings                                                                                         | no       | The names the affix is read from.                                                                                                                                                                                                                                                                                                        |
 | `data.affixes[].barredAfter`              | a list of sounds                                                                                          | no       | The sounds a stem may not close on to take the affix.                                                                                                                                                                                                                                                                                    |
 | `data.affixes[].tones`                    | a tone pattern, such as `L`                                                                               | no       | The tone pattern the affix carries, written as a word's `tones` is.                                                                                                                                                                                                                                                                      |
+| `data.affixes[].native`                   | a list of `{ map, font?, text }`                                                                          | no       | The affix's writing under a logographic map, which a word whose `built` names the affix is written with.                                                                                                                                                                                                                                 |
+| `data.affixes[].native[].map`             | a mapping note's `data.map.name`                                                                          | yes      | The map the native form is written for.                                                                                                                                                                                                                                                                                                  |
+| `data.affixes[].native[].font`            | a face the map lists                                                                                      | no       | The one face the native form is for; unstated, it is for every face the map lists, and a form stated for a face wins over it there.                                                                                                                                                                                                      |
+| `data.affixes[].native[].text`            | the word in the script, as the map's characters                                                           | yes      | The word as the script writes it, where the map's rows would write it otherwise, or as a logographic map writes it.                                                                                                                                                                                                                      |
 | `data.grammar.plural`                     | list of `{ ending, becomes }`                                                                             | no       | Default noun plurals, replacing the first matching literal ending in authored order. A word's explicit plural wins; no word is checked against this rule.                                                                                                                                                                                |
 | `data.grammar.plural[].ending`            | a literal ending string, which may be empty                                                               | yes      | The bare suffix replaced by this rule; empty matches every noun.                                                                                                                                                                                                                                                                         |
 | `data.grammar.plural[].becomes`           | a literal ending string, which may be empty                                                               | yes      | The bare replacement; empty removes the matching suffix.                                                                                                                                                                                                                                                                                 |
@@ -544,6 +552,11 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.grammar.participles`                | a map — `{ root, affixes }`                                                                               | no       | Participles on the verb root: a verb closing on a `root` ending drops it, and each named suffix attaches to what is left; a participle closing on an `agreement` ending agrees. Read by the mapped-run word check.                                                                                                                       |
 | `data.grammar.participles.root`           | a list of closing letters, such as `[athen, ethen]`                                                       | yes      | The infinitive endings a verb's citation form drops to give its root, the longest that matches first. A verb closing on none has no participle.                                                                                                                                                                                          |
 | `data.grammar.participles.affixes`        | a list of suffixes of `data.affixes`, such as `[-andar, -thos]`                                           | yes      | The participle suffixes, each attaching to the root as its own `replaces` says: `vowel` or letters take the place of the root's close, and none adds it whole.                                                                                                                                                                           |
+| `data.grammar.native`                     | a list of `{ ending, map, font?, text }`                                                                  | no       | Under a logographic map, the signs a noun's plural or a verb's present form is written with after its stem's writing, one entry per ending, map and face.                                                                                                                                                                                |
+| `data.grammar.native[].ending`            | one of plural, I, you, heShe, we, youAll, they                                                            | yes      | The ending written: `plural` for a noun's plural, or a person of `verbs.persons` for a verb's present form.                                                                                                                                                                                                                              |
+| `data.grammar.native[].map`               | a logographic mapping note's `data.map.name`                                                              | yes      | The logographic map the ending is written for.                                                                                                                                                                                                                                                                                           |
+| `data.grammar.native[].font`              | a face the map lists                                                                                      | no       | The one face the writing is for; unstated, it is for every face the map lists, and a writing stated for a face wins over it there.                                                                                                                                                                                                       |
+| `data.grammar.native[].text`              | the ending in the script, as the map's characters; empty writes the stem alone                            | yes      | The signs written after the stem's writing.                                                                                                                                                                                                                                                                                              |
 | `data.tongues[].tag`                      | a tag such as `dunhari`, or `exonym:<tongue>`                                                             | yes      | The tag a register row's `tongue` names: lowercase letters and digits, or a tag closing on `:<tongue>`, which declares one tag per tongue named after the colon.                                                                                                                                                                         |
 | `data.tongues[].meaning`                  | a string                                                                                                  | yes      | What a name of this tongue is.                                                                                                                                                                                                                                                                                                           |
 | `data.tongues[].language`                 | a language skill Address                                                                                  | no       | The language note the tag names, where it is one.                                                                                                                                                                                                                                                                                        |
@@ -579,7 +592,10 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.sounds.clusters.groups[].what`      | a string, such as `a nasal and a fricative`                                                               | yes      | What the clusters of the group are made of.                                                                                                                                                                                                                                                                                              |
 | `data.sounds.clusters.groups[].clusters`  | a list of clusters                                                                                        | yes      | The clusters, as written; a digraph counts as one consonant.                                                                                                                                                                                                                                                                             |
 | `data.sounds.clusters.groups[].use`       | one of common, sparing                                                                                    | yes      | How often the group's clusters stand inside a word.                                                                                                                                                                                                                                                                                      |
-| `data.sounds.stress`                      | one of first syllable, penultimate or final, by weight, as marked                                         | no       | Where a word's stress falls.                                                                                                                                                                                                                                                                                                             |
+| `data.sounds.stress`                      | a map — `{ two, longer, mark? }`                                                                          | no       | Where a word's stress falls, as a rule a program reads.                                                                                                                                                                                                                                                                                  |
+| `data.sounds.stress.two`                  | one of first, last                                                                                        | yes      | The stressed syllable of a word of two syllables.                                                                                                                                                                                                                                                                                        |
+| `data.sounds.stress.longer`               | one of antepenultimate, penultimate, final                                                                | yes      | The stressed syllable of a word of three or more, counted from its end.                                                                                                                                                                                                                                                                  |
+| `data.sounds.stress.mark`                 | one of acute, grave, circumflex                                                                           | no       | The diacritic that marks a stress the rule would not choose; it moves the stress to the syllable it sits on.                                                                                                                                                                                                                             |
 | `data.sounds.finals`                      | list of `{ final, like }`                                                                                 | no       | The syllable finals, for a language whose syllables are parsed by them.                                                                                                                                                                                                                                                                  |
 | `data.sounds.finals[].final`              | a final as written, such as `ang`                                                                         | yes      | The final.                                                                                                                                                                                                                                                                                                                               |
 | `data.sounds.finals[].like`               | a string                                                                                                  | yes      | What it sounds like.                                                                                                                                                                                                                                                                                                                     |
@@ -691,6 +707,9 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.naming.nearName.examples`           | list of `{ near, given }`                                                                                 | no       | Worked near names, each beside its given name.                                                                                                                                                                                                                                                                                           |
 | `data.naming.nearName.examples[].near`    | a near name, such as `Anlâ`                                                                               | yes      | The near name.                                                                                                                                                                                                                                                                                                                           |
 | `data.naming.nearName.examples[].given`   | a given name                                                                                              | yes      | The given name it is the near name of.                                                                                                                                                                                                                                                                                                   |
+| `data.script.fonts`                       | list of installed faces' slugs                                                                            | yes      | The faces the script is written in, by the slug `font=` names them by. A face belongs to one script.                                                                                                                                                                                                                                     |
+| `data.script.emphasis`                    | `rubric` or `overline`                                                                                    | yes      | How the script marks a stressed word: `rubric` sets it in red, `overline` draws a line above it. It sets `*…*` and `**…**` inside a run in one of its faces, unless the run's language states its own `emphasis`.                                                                                                                        |
+| `data.script.strongEmphasis`              | `rubric` or `overline`                                                                                    | no       | The convention `**…**` takes instead of `emphasis`'s.                                                                                                                                                                                                                                                                                    |
 
 **System mappings**
 
@@ -972,18 +991,26 @@ Lore records in-world knowledge. A `culture` describes a people; a `custom` desc
 
 ### doc
 
-**Subtypes:** `rules`, `userguide`, `reference`, `howto`, `concept`, `settingguide`.
+**Subtypes:** `rules`, `userguide`, `reference`, `howto`, `concept`, `settingguide`, `post`.
 
-| Field          | Shape                                    | Meaning                                                                                                                                     |
-| -------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `data.culture` | an Address                               | The culture a setting guide introduces, as a culture lore note. Required on `settingguide`; no other subType states it.                     |
-| `data.map`     | a map — `{ name, vowels?, fonts, rows }` | A mapping, which text marked `map=` with its `name` is rewritten by before it is set. See [mapping notes](format-details.md#mapping-notes). |
+| Field           | Shape                                                  | Meaning                                                                                                                                                                    |
+| --------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `data.concepts` | list of `{ id, gloss, group }`                         | The concepts of a core vocabulary, in the order the report lists them. See [the core vocabulary](format-details.md#the-core-vocabulary).                                   |
+| `data.date`     | string                                                 | The day a post was published, as `YYYY-MM-DD`. Required on a `post`; no other subType states it. Posts are listed and fed newest first by it.                              |
+| `data.author`   | string                                                 | Who wrote a post, as the byline prints them. A post that names none carries the site's byline, the first entry of `authors`; no other subType states it.                   |
+| `data.culture`  | an Address                                             | The culture a setting guide introduces, as a culture lore note. Required on `settingguide`; no other subType states it.                                                    |
+| `data.map`      | a map — `{ name, logographic?, vowels?, fonts, rows }` | A mapping, which text marked `map=` with its `name` is rewritten by before it is set. See [mapping notes](format-details.md#mapping-notes).                                |
+| `data.metres`   | list of `{ name, beats, kind }`                        | The metres a verse fence's `scan=` names. A fence that states one is warned at each line that cannot have its beats. See [metres](../authoring/links-and-markup.md#metre). |
 
 **Inner keys** — a key a field's value does not declare is an error at its own line and column.
 
 | Key                              | Shape                                                | Required | Meaning                                                                                                                                                                                                |
 | -------------------------------- | ---------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `data.concepts[].id`             | lowercase letters, digits and `-`                    | yes      | The concept's id, which a word's `concept` names. Unique in the package.                                                                                                                               |
+| `data.concepts[].gloss`          | a short gloss, such as `a smell; a scent`            | yes      | What the concept means, in brief.                                                                                                                                                                      |
+| `data.concepts[].group`          | a group name, such as `senses`                       | yes      | The group the report lists the concept under.                                                                                                                                                          |
 | `data.map.name`                  | string                                               | yes      | What `map=` names the map by: lowercase letters, digits and `-`, unique in the package.                                                                                                                |
+| `data.map.logographic`           | `true`                                               | no       | The script writes meanings: a mapped run's words are written by the language's lexicon alone, and the rows write only the text between them.                                                           |
 | `data.map.vowels`                | string                                               | no       | The characters a row's `before: vowel` reads as vowels; any other letter is a consonant.                                                                                                               |
 | `data.map.rows`                  | list of `[from, to]` or `{ from, to, before?, at? }` | yes      | The rewrites, each `[from, to]` or `{ from, to, before?, at? }`: `before` is `vowel` or `consonant`, `at` is `start` or `end`. The longest `from` wins, and a character no row matches passes through. |
 | `data.map.rows[].from`           | a string of one or more characters                   | yes      | The one or more characters the row matches.                                                                                                                                                            |
@@ -997,6 +1024,9 @@ Lore records in-world knowledge. A `culture` describes a people; a `custom` desc
 | `data.map.fonts[].rows[].to`     | a string, which may be empty                         | yes      | What the row writes in their place; empty to drop them.                                                                                                                                                |
 | `data.map.fonts[].rows[].before` | string                                               | no       | `vowel` or `consonant`: what must follow the match for the row to apply.                                                                                                                               |
 | `data.map.fonts[].rows[].at`     | string                                               | no       | `start` or `end`: where the match must sit for the row to apply.                                                                                                                                       |
+| `data.metres[].name`             | string                                               | yes      | What a verse fence's `scan=` names the metre by: lowercase letters, digits and `-`, unique in the package.                                                                                             |
+| `data.metres[].beats`            | a whole number above zero                            | yes      | The beats of one line.                                                                                                                                                                                 |
+| `data.metres[].kind`             | one of accentual                                     | yes      | How the beats are counted: `accentual`, one beat for each stressed syllable the language's stress rule and the beat convention give.                                                                   |
 
 ### macro
 

package/docs/reference/theme-pages.md

@@ -7,8 +7,9 @@ subType: reference
 
 # What the theme draws
 
-`package-build site` writes a page's front matter; the shared Hugo theme reads
-it and draws the page around it. This reference describes that second half —
+`package-build site build` settles a page's front matter and body; the shared
+site theme draws the page around them. This reference describes that second
+half —
 the infobox rail, the hero band, the generated sections, the related card,
 search, and the markup an image or a figure renders as — and names the
 classes a consumer styles against.
@@ -30,7 +31,7 @@ A place’s Government row links to its authored governing affiliation. Explicit
 The toolchain settles what each box holds and in what order — see
 [the infobox](format-details.md#the-infobox) for the field semantics, the
 three states a system box can say, and the four section layouts a box is
-built from. On the website, `partials/infobox.html` draws the whole list by
+built from. On the website, the `infobox` partial draws the whole list by
 switching on a section's `layout` and a value's `kind`, never on a note type
 or a field name:
 
@@ -121,13 +122,13 @@ A page whose front matter declares no `infoboxes:` renders no rail.
 
 ## The hero banner
 
-Nearly every page opens with a hero band, and `partials/hero-banner.html`
+Nearly every page opens with a hero band, and the `hero-banner` partial
 decides what sits behind it. A page arrives with its hero image stated in one
 of two ways, and the difference is who resolved it: a content page carries
 `data.banner`, which the build resolved from the asset Address the note
 declared into the address its asset host serves; a hand-authored page carries
 a top-level `banner:`, which the theme resolves against `params.cdnBaseURL`
-(see [`params.cdnBaseURL`](../configuration.md#the-generated-hugo-configuration)).
+(see [`params.cdnBaseURL`](../configuration.md#what-the-site-build-reads)).
 
 **Resolution order.**
 
@@ -143,13 +144,13 @@ a top-level `banner:`, which the theme resolves against `params.cdnBaseURL`
 4. `images/banners/default.webp` — when the page has no type, **and** whenever
    the name picked by 2 or 3 is not in the declared inventory.
 
-**Why step 4 is a declaration, not a test.** Hugo cannot ask a remote host
-whether a URL exists, so a banner that was never drawn would 404 in silence —
-the band renders with its title, palette and gradient intact behind a dead URL,
-and nothing fails: not the build, not Hugo, not the deploy guard.
-`data/banners.yaml` is the declaration that stands in for the test the
-template cannot make. A name listed in its `available` is asserted to exist; a
-resolved name that is absent falls back to `fallback`, and Hugo logs one
+**Why step 4 is a declaration, not a test.** The build cannot ask a remote
+host whether a URL exists, so a banner that was never drawn would 404 in
+silence — the band renders with its title, palette and gradient intact behind
+a dead URL, and nothing fails: not the build, not the deploy guard.
+`banners.yaml` is the declaration that stands in for the test the template
+cannot make. A name listed in its `available` is asserted to exist; a resolved
+name that is absent falls back to `fallback`, and the build reports one
 deduplicated warning naming the missing banner and the first page that wanted
 it. The fallback applies only to a relative path landing directly in the
 declared `dir` — an absolute URL, and a fragment pointing anywhere else under
@@ -158,7 +159,7 @@ either and must not second-guess an address it cannot know about. A step 1
 address is not checked for the same reason: the question has already been
 answered upstream.
 
-**The kind mapping.** `data/banner-kinds.yaml` declares, once, which banner a
+**The kind mapping.** `banner-kinds.yaml` declares, once, which banner a
 page of each note `type` opens with. A type maps to one banner name for all of
 its subTypes, or to a table that names a banner for every subType the note
 vocabulary declares for it:
@@ -178,20 +179,15 @@ kinds:
 warning. A type missing from the file resolves to its own name, so a kind with
 no declared art still produces the missing-banner warning. The lint check and
 the test suite fail on a mapped name that `banners.yaml` does not declare, and
-on a type or subType of the note vocabulary that the mapping omits. A consumer
-publishing its own artwork set ships its own `data/banner-kinds.yaml` beside
-its `data/banners.yaml`.
+on a type or subType of the note vocabulary that the mapping omits.
 
-**One resolver.** The order above lives in `partials/banner-url.html`, which
-returns a URL or an empty string; `hero-banner.html` calls it with the page's
-`type`, `subType` and `category`, for step 3.
+**One resolver.** The order above lives in one function of the engine, which
+returns a URL or an empty string; the `hero-banner` partial is given the
+result.
 
-**Keeping the inventory honest.** The lint check over `data/banners.yaml`
-fetches every declared name from the asset host and fails on any non-200
-response, so a name added optimistically is caught here rather than on a
-published page. A consumer publishing its own artwork set replaces the whole
-list by shipping its own `data/banners.yaml`, which Hugo reads in preference
-to the theme's bundled one, and can run the same check against it.
+**Keeping the inventory honest.** The lint check over `banners.yaml` fetches
+every declared name from the asset host and fails on any non-200 response, so
+a name added optimistically is caught here rather than on a published page.
 
 **Declining a hero image.** `banner: none` on a hand-authored page, and a
 blank `data.banner` on a note (which the build emits for `data.banner: none`),
@@ -246,7 +242,7 @@ is the way to choose different contents for one, or to turn one off.
 
 ## The related card
 
-`partials/related.html` renders a bordered "Related" card below the body,
+The `related` partial renders a bordered "Related" card below the body,
 listing the pages connected to this one. The build emits this front matter on
 every content page; what links to a page is a fact about every other page, so
 an authored `related:` is refused and dropped:
@@ -386,13 +382,37 @@ stacks as well. The Foundry stylesheet draws the same.
 | `.verse-part`      | one entry's text, in the body serif unless its face sets it   |
 | `.verse-secondary` | every entry after a column's first, muted                     |
 
+## Emphasis in a script
+
+Emphasis inside a run set in a face stays an `<em>` or a `<strong>`, and its
+class names the convention its language or script states (see
+[script notes and emphasis](format-details.md#script-notes-and-emphasis)):
+
+| class            | drawn as                      |
+| ---------------- | ----------------------------- |
+| `.emph-rubric`   | the text in `var(--rubric)`   |
+| `.emph-overline` | the text with a line above it |
+
+`.script em` and `.script strong` keep the face's Regular: no slant, no added
+weight, and `font-synthesis: none`. A script whose notes state no convention
+gives a bare `<em>` or `<strong>`, which therefore looks like the text around
+it.
+
+The theme's `--rubric` is `#e0705f`, a warm red for its dark ground. Because a
+rubric carries emphasis by colour alone, it holds 4.5:1 against `--bg`,
+`--bg-card` and `--surface`, and 1.75:1 against `--text`, so a reader who
+cannot see its hue still sees a lighter or darker word. A site that overrides
+`--rubric` keeps both. Foundry's base stylesheet sets the same classes from
+`--pb-rubric`, `light-dark(#9c281b, #e0705f)`, against Foundry's journal page in
+each theme, and the book prints its rubric in `#9c281b` on its paper.
+
 ## Search
 
 `params.search = true` renders a search box in the header; left unset (or
-`false`), `partials/search.html` renders nothing. The box, and everything it
+`false`), the `search` partial renders nothing. The box, and everything it
 opens, is the theme's own — the index it reads is not.
 
-**Where the index comes from.** `package-build site-root` writes a
+**Where the index comes from.** `package-build site build` writes a
 [Pagefind](https://pagefind.app) index at `pagefind/` beside the rendered
 pages, when `site.search` in `package-build.config.yaml` is left at its
 default of `true` (see [`site.search`](../configuration.md#site) and
@@ -403,26 +423,40 @@ Pagefind version. Turning `params.search` on without `site.search` indexing
 the site (or with it set `false`) shows an empty results box that never finds
 anything — the two settings are independent, and a consumer sets both.
 
-Both files are referenced the same way every other theme-bundled asset is —
-`relURL`, the same resolution `"css/style.css" | relURL` uses in
-`baseof.html` — so a package served under a prefix (`/thalorna/pagefind/…`)
-finds its own index rather than another package's, and the theme carries no
-address of its own.
+Both files are addressed relative to the site's base, so a package served
+under a prefix (`/thalorna/pagefind/…`) finds its own index rather than
+another package's, and the theme carries no address of its own.
 
 **Why a header box and not a `/search/` page.** A site is its homepage and
 its pages, with nothing generated between them — a results page would need a
-consumer content file at that address, which the theme has no way to
-conjure. Pagefind's own panel UI needs no page of its own: the header button
-opens it in place.
-
-**What is indexed.** `data-pagefind-body` on `.single-body` scopes indexing to
-a page's prose; the theme's own chrome carries `data-pagefind-ignore` — the
-header, the footer, the infobox rail, the table of contents, the Related
-card, and the hero banner's title and tagline. `_default/single.html` also
-tags every page with `data-pagefind-filter="type"` and
-`data-pagefind-filter="package"`, read from the page's own `type` and
-`package` front matter, so a search can be narrowed to one catalog or one
-package without either value appearing in the page itself.
+note at that address. Pagefind's own panel UI needs no page of its own: the
+header button opens it in place.
+
+**What is indexed.** `data-pagefind-body` on a page's prose scopes indexing to
+it; the theme's own chrome carries `data-pagefind-ignore` — the header, the
+footer, the infobox rail, the table of contents, the Related card, and the
+hero banner's title and tagline.
+
+**What a page tells the search.** Each page carries hidden metadata the
+search reads: its title, its filters, its aliases, its picture and, for a
+post, its date.
+
+| Filter      | Values                                       |
+| ----------- | -------------------------------------------- |
+| `package`   | the package that publishes the note          |
+| `type`      | the note's `type`                            |
+| `subtype`   | the note's `subType`                         |
+| `culture`   | the name of the culture `data.culture` names |
+| `continent` | the continent the note lies in               |
+| `region`    | the outermost region beneath that continent  |
+
+A post carries `author` and `tags` filters and sorts by its `date`. A note's
+name and its aliases count ten times a word of its body, so a search for a name
+opens that note first and a search for an alias finds it. A result shows the
+note's `data.icon`, or its hero banner where it has none. A note's tags and its
+draft state are not filters. Secret blocks, inline secrets and `.secret`
+sections are kept out of the index. [The site guide](../guides/site.md#search)
+says where a note lies and how a merged search reads other sites' indexes.
 
 **Classes added:** `.site-search`, `.search-toggle`, `.search-panel`,
 `.search-panel-inner`, and `.header-actions` (the header's nav/search/toggle
@@ -430,20 +464,20 @@ group). `.search-panel-inner` carries Pagefind's own `--pagefind-ui-*`
 theming variables, set from the theme's own tokens so results match the
 chrome around them.
 
-## What a page, a homepage and a section landing carry
+## What a page, a homepage and a listing carry
 
 ### A page
 
-`_default/single.html` renders every page that is not the homepage: the hero,
-the infobox rail, the body, any `related:` block, and prev/next links through
-the page's own catalog.
+The `page` layout draws every note that is not the homepage: the hero, the
+infobox rail, the body, any `related:` block, and prev/next links through the
+page's own catalog.
 
 **Emitted.** A note's page arrives with `title` (the note's name), `type`,
 `subType`, `description` and `tags` already set, and `data.banner` resolved.
-The form below is the hand-written one, which is what a blog post or a
-curated landing carries: `title`, `date` and a top-level `banner:` are keys
-the content build never writes, and a note's page therefore has no `date` and
-no meta-line date at all.
+The form below is the hand-written one, which is what a curated landing
+carries: `title`, `date` and a top-level `banner:` are keys the content build
+never writes, and a note's page therefore has no `date` and no meta-line date
+at all.
 
 ```yaml
 ---
@@ -459,13 +493,13 @@ tags: [archetype, mercantyl] # optional; shown in the page meta line
 
 - **`type`** is the page's catalog key, unless it is `doc` — prose rather than
   a catalog of its own — in which case the key is `subType` (what the build
-  compiles from a note's classification) or, failing that, `category` (what a
-  hand-mounted documentation tree carries). A page with no `type` has no
-  catalog.
+  compiles from a note's classification) or, failing that, `category`. A page
+  with no `type` has no catalog.
 - **`date`**, **`tags`** — each optional and shown only when present, in a
-  meta line above the body. A tag links to `tags/<tag>/`.
+  meta line above the body. A tag links to `tags/<tag>/` where the site writes
+  a page for each tag (`site.tags`), and is plain text otherwise.
 - **`subType`** — shown as a plain label for `type: being` pages. It does not
-  create a tag or taxonomy term.
+  create a tag.
 
 **The draft notice.** A page tagged `draft` states that its content is not
 settled, at the head of the article — above the infobox rail and above the
@@ -484,29 +518,34 @@ out of the meta line's tag row and said here instead.
   it states may change, and nothing in it is settled._
 - **`.draft-notice`**, **`.draft-notice-icon`**, **`.draft-notice-text`** and
   **`.draft-notice-label`** are the classes a consumer styles against.
-- The mark is Font Awesome, which `baseof.html` already loads; the sentence
+- The mark is Font Awesome, which the base layout already loads; the sentence
   reads on its own where it does not arrive.
 - The sentence is an `em`: the label is the page's own voice naming the
   state, and the sentence is the page speaking about itself.
 - A page carrying the notice also carries **`.single-with-notice`** on its
   article, which is what moves a two-column page's content and rail below it.
 
-**Prev/next.** `.PrevInSection` / `.NextInSection` walk every page under the
-site's content mount, since the build emits every note flat there rather than
-filing it into a directory named for its catalog. A mount holding more than
-one catalog narrows the walk to the pages sharing this page's catalog key, so
-reading through the afflictions does not surface a skill; a mount holding a
-single catalog is untouched, because `.PrevInSection` already walks exactly
-that catalog there.
+**Prev/next.** The links walk the pages of the site in the order a reader
+walks them. A site holding more than one catalog narrows the walk to the pages
+sharing this page's catalog key, so reading through the afflictions does not
+surface a skill; a site holding a single catalog is untouched.
+
+### A post
+
+A note of `type: doc` and `subType: post` is drawn by the `blog-post` layout:
+the post's title, its date and writer, its series where it states one, its
+tags, and its body. Posts are listed newest first on the page of the section
+`site.feed` names, and the site writes an Atom feed beside that page.
 
 ### The homepage
 
-A package's home page is `content/_index.md`, mounted at the package's own
-prefix. `layouts/index.html` selects between two shapes by what it carries.
+A package's home page is the `type: homepage` note, drawn by the `home`
+layout at the package root. The layout selects between two shapes by what the
+page carries.
 
 **`type: homepage`** renders the page through the same structure a note gets
-from `_default/single.html` — the hero from its `banner:`, then its body —
-sharing the markup through `partials/page-body.html` so a homepage and a page
+from the `page` layout — the hero from its `banner:`, then its body —
+sharing the markup through the `page-body` partial so a homepage and a page
 read as one family:
 
 ```yaml
@@ -516,11 +555,10 @@ title: Song of Heroic Lands # hero heading
 description: A classless, skill-based fantasy system … # hero standfirst
 
 # The hero image. The same `banner:` every other page in this theme uses,
-# resolved by `partials/hero-banner.html` in the documented order and through
-# `params.cdnBaseURL` — see "The hero banner" above. With none set, the
-# subtype default lands on `images/banners/homepage.webp`, since the subtype
-# default is keyed on the page's `type`. `banner: none` declines a hero image
-# entirely.
+# resolved in the documented order and through `params.cdnBaseURL` — see "The
+# hero banner" above. With none set, the subtype default lands on
+# `images/banners/homepage.webp`, since the subtype default is keyed on the
+# page's `type`. `banner: none` declines a hero image entirely.
 banner: brand/sohl-banner.webp
 ---
 Everything published for the system lives under this address …
@@ -530,39 +568,20 @@ The home page declares no `infoboxes:`, `related:`, `date:` or `tags:`, so
 those pieces of a page stay silent.
 
 **No `type` at all** — a site whose home page is a set of entry points into
-everything it publishes — renders the featured grid from `params.home`.
-A package-build configuration supplies those values through
-[`site.hugo`](../configuration.md#site).
-
-### A section landing
-
-**Hand-written.** `_default/list.html` renders whatever a consumer still
-gives Hugo's `section`, `taxonomy` or `term` kinds to render — a
-hand-curated landing at a real subdirectory, and Hugo's own tag pages. A
-`package-build` site disables all three (`disableKinds`), so this layout
-never runs for one; a site that keeps them enabled still needs a landing, and
-this is it.
-
-It opens with the hero and any authored body, then auto-lists the section's
-members (`.Pages`) as a gap-filler: a member the body already links,
-directly or transitively, is not repeated, and the rest appear under
-"Orphaned Pages" when the body links some of them, or plainly when it links
-none. A tag's term page lists the pages carrying it; the tag index itself
-lists every tag with its page count.
-
-```yaml
----
-# content/projects/_index.md — a hand-curated landing, no `type:` at all
-title: Projects
-description: Foundry VTT systems, modules, and reference content …
----
-Each section below has its own landing page.
-
-# [Song of Heroic Lands](/projects/song-of-heroic-lands/)
-…
-```
-
-A row is a linked title and, when the page carries one, its description.
+everything it publishes — renders the featured grid from `params.home`: a hero
+(`heroimage`, `herotitle`, `herotagline`), the section headings, and a card for
+each entry of `cards`, each with a title, an address, a line of text and an
+optional image.
+
+### A listing
+
+The `list` layout draws a page that lists other pages: a section a note
+stands for (`site.sections`), and the tag pages `site.tags` writes. It opens
+with the hero and any authored body, then lists the members the body does not
+already link, directly or transitively, under a heading when the body links
+some of them, or plainly when it links none. A tag's page lists the pages
+carrying it; the tag index lists every tag with its page count. A row is a
+linked title and, when the page carries one, its description.
 
 ## Alerts
 

package/docs/source-preview.md

@@ -9,7 +9,8 @@ subType: reference
 
 Preview renders only the supplied Markdown buffer. It works with ordinary
 Markdown, optional YAML frontmatter, and local Heroic Lands extensions, without
-configuration, a content tree, dependency caches, a content index or Pandoc.
+configuration, a content tree, dependency caches, a content index or Pandoc. A
+host that holds a content index can give it to the preview for a fuller view.
 
 ```sh
 package-build-preview < note.md > preview.html
@@ -25,6 +26,19 @@ is the default; `--dark` is explicit and independent of browser preferences.
 options. Unsupported arguments exit 1. Findings go to stderr; success exits 0,
 and render errors exit 1. A partial preview may accompany error findings.
 
+Preview renders through the same renderer as the packs and the websites, so an
+alert, a secret block, a verse, a captioned item, a footnote section and a
+picture's size and position read as they do on those surfaces. Fenced code that
+names a language is highlighted. A tag written in a note is shown as text.
+
+The default view needs no content index, so it shows what it cannot resolve as
+source. A host that holds the package's content index builds an index with
+`previewIndex` and passes it to `renderPreview` as `index`. Rendered that way, a
+wikilink is a link, a link to a concealed note is concealed, an embed draws its
+picture, marked text is mapped and set in its face, an icon is drawn, and a
+caption is numbered with its asset's role, so a map is a **Map**. A query, which
+a buffer cannot run, stays highlighted source in both views.
+
 Wikilinks, image and portrait links retain their complete source: blue brackets,
 purple addresses, bold foreground labels and grey attributes. Entire spans are bold, including their visible brackets and attributes.
 Definition-list terms are bold and definitions use normal text. SQL and pagelist fences remain grey source;