A–Z index
1,019 words used in the documentation. 252 have a written page, the others exist through their uses alone.
Filters
L53 words
| Word | Type | First line of the page, or most cited passage | Pages |
|---|---|---|---|
| label | no definition | “…ll title staying in the list below. The layout is deterministic and the same labels never overlap: the tool estimates the width of every label, pushes apart any…” — Neighbourhood map | 27 |
| label overrides | no definition | “…ght and dark palettes, checked for contrast at build. Footer text, footer links, an extra stylesheet, label overrides. Theme override model · 2026-08-27 · 3/6” — Theme override model | 3 |
| labelled | no definition | “…then the attributes the type declares in the order of its declaration, each labelled as the profile says in the language of the site, the values of a list separ…” — Entity page | 3 |
| lack | no definition | “…rse. It names the cause in plain words, says what stays reachable despite the lack, and offers at least two ways out; no partial lack hides the rest of the page…” — Edge cases | 2 |
| language | no definition | “A language is described by data, never by code: a folder holding pack.yaml (the name of the language, its apostrophes, its collation options, its plural suffix …” — Adding a language pack | 22 |
| language of the site | no definition | “…he order of its declaration, each labelled as the profile says in the language of the site, the values of a list separated by commas, with the note "N declared …” — Entity page | 3 |
| Language pack | Term | The data that describes a language to the engine, never code: a folder holding pack.yaml (the name of the language, its apostrophes, its collation options, its plural suffix rules, validated by… | 18 |
| language, its apostrophes | no definition | “…by data, never by code: a folder holding pack.yaml (the name of the language, its apostrophes, its collation options, its plural suffix rules, validated by the …” — Adding a language pack | 2 |
| layers | no definition | “Layers: the stylesheet of the project is loaded last, in the fourth cascade layer, so that nothing in the default theme can outrank it.” — Theme override model | 5 |
| layers Named slots | no definition | “Slots, islands and layers: named slots with typed view models, islands for the interactive parts only, cascade layers so that the project stylesheet wins by con…” — Theme override model | 4 |
| layers: tokens | no definition | “…ll bundle per island: search, mentions panel, mode switch. Four cascade layers: tokens, base, components, project. The project stylesheet is loaded last and w…” — Theme override model | 4 |
| layers: tokens, base | no definition | “…bundle per island: search, mentions panel, mode switch. Four cascade layers: tokens, base, components, project. The project stylesheet is loaded last and wins…” — Theme override model | 4 |
| layers: tokens, base, components | no definition | “… per island: search, mentions panel, mode switch. Four cascade layers: tokens, base, components, project. The project stylesheet is loaded last and wins by co…” — Theme override model | 4 |
| Legal declaration | Term | What only the organisation that publishes a site can say, and what the tool therefore never pre-fills: its legal notice, its accessibility statement with the compliance it declares, non compliant,… | 4 |
| letter | no definition | “Every word the documentation uses, with or without a definition, by initial letter. Letters without an entry stay in view, struck through and inert. Each word i…” — Alphabetical index | 5 |
| licence | no definition | “…is published under the GNU General Public License, version 3 or later, and a licence inventory of the dependencies is regenerated and verified before every rele…” — GPL-3.0-or-later | 6 |
| licence inventory | no definition | “…lease with the standalone binaries of the linter, the checksums and the licence inventory, and the same tarballs go to npm, the container image to its registry …” — Release | 4 |
| lies | no definition | “…n_neighbours is a pivot; every note no frontmatter, folder or glob files that lies within radius edges of a pivot is a candidate for a domain named after it, at…” — Emergent domain | 3 |
| light | no definition | “The switch of the bar of every page that takes the site from its light palette to its dark one and back. The dark scheme is a second palette, not an inversion o…” — Colour scheme | 10 |
| Link | Term | A typed relation between two entities, carrying a confidence and at least one provenance. A link is produced by a written markdown link, a frontmatter reference, a mention in a mapped section, an… | 35 |
| Link | Term | A markdown link written by an author in a note, such as [publication threshold](../rules/publication-threshold.rule.md). It is the strongest evidence the tool knows: a written link produces a typed… | 27 |
| Link | Business object | A typed relation between two entities, carrying a confidence between 0 and 1 and at least one provenance: method, file, line, section, context. When several methods produce the same source, target… | 175 |
| link an author | no definition | “…rds around the citation and a link to the passage. A mention is either a link an author wrote, in the text or in the frontmatter, or a recognised word the scan …” — Mention | 3 |
| Link checks | Term | The check family of what a note points at: E-LINK-BROKEN, a markdown link to a file that does not exist in its source; W-LINK-CROSS-SOURCE, a link into another source while… | 15 |
| link of the model | no definition | “A neighbour of the neighbourhood panel, which comes from a link of the model; an accompanying word comes from shared paragraphs alone.” — Accompanying word | 3 |
| links across sources | no definition | “…rt_terms and type_prefixes for the dictionary; cross_source_links for links across sources; ngrams and candidate_score for the candidate expressions; keyword_pa…” — Inference | 3 |
| links and recognised | no definition | “…entry per page that evokes the entity, by number of passages, written links and recognised words counted alike, each entry marked "Cited" when the page writes a…” — Entity page | 3 |
| links and the co | no definition | “…y term with a note of its own whose distinct neighbours, over the typed links and the co-occurrences, reach min_neighbours is a pivot; every note no frontmatter…” — Emergent domain | 3 |
| Links are authoritative | Decision | A markdown link to another note is the strongest relation the tool knows: confidence 1.00, above anything inferred, and a frontmatter reference comes next at 0.90. What an author wrote is never… | 0 |
| Links block | Data object | The links block of the canonical model: one object per source, target and relation triple, in that order, with the attributes of the relation, the combined confidence and the complete list of what… | 10 |
| links pointing | no definition | “…cases remain to frame: a page whose file is empty, and a repository that became unreachable, whose pages vanish while the links pointing at them do not know it.” — Edge cases | 3 |
| Lint | Process | concordance lint runs the same checks as the build pipeline on a single knowledge repository, before any site exists. In local scope it needs no network and writes nothing unless asked to fix. In… | 80 |
| lint package | no definition | “…ween the two types, or a title shared with an entity of another type. The lint package lists them as GLOBAL_CHECKS (E-LINK-BROKEN, E-META-REL, I-TERM-HOMONYM, W…” — Global check | 3 |
| Linter | Term | The lint command: it reads every markdown file of one knowledge repository but the excluded ones, runs the checks that a repository can be held to alone, and prints one line per finding with the… | 46 |
| Linter and build parity | Business rule | The local lint says the same thing as the build. For the checks the linter computes in --scope repo, listed as LOCAL_CHECKS by the lint package (E-ENCODING, E-FM-INVALID, E-ID-DUP, E-ID-INVALID,… | 26 |
| linter where the notes | no definition | “Quality: a linter where the notes are written, the same checks in the merge request and in the build, a SARIF log in the margin of the diff; the wiki keeps pace…” — Roadmap outline | 3 |
| List the entities | Operation | Returns the entities of the last build, in identifier order, with the same fields as the entities block of the model; a screen that cannot read model.json directly will page through them here. The… | 23 |
| loading | no definition | “The first draft of the theme named its font families by loading them from a public font host, as most static sites do: one stylesheet link, no file to ship. Sup…” — Fonts from a third-party host | 3 |
| local | no definition | “…e build pipeline on a single knowledge repository, before any site exists. In local scope it needs no network and writes nothing unless asked to fix. In global …” — Lint | 19 |
| Local check | Term | A check the linter computes on one repository alone, without the network and without the rest of the model: encoding, frontmatter, identifiers and internal links. The lint package lists them as… | 27 |
| local storage | no definition | “…sing the switch displays the other scheme at once and remembers it in the local storage of the browser under concordance-mode, so that the next page and the nex…” — Colour scheme | 3 |
| Locale | Term | The language of a source or of the project, written as a BCP 47 tag, en, fr, fr-CA. The locale of a source selects its language pack, the type prefixes of the profile for that language and the… | 22 |
| Locale per source | Decision | Each source declares its locale as a BCP 47 tag, defaulting to the project locale. A language is described by data, never by code: a pack holding its name, its apostrophes, its collation options, its… | 0 |
| Lock | Term | A versioned file in the configuration repository, concordance.lock.yaml, named by the lock key of the configuration, that records human decisions: accepted and rejected links, merged and separated… | 28 |
| Lock file for human decisions | Decision | concordance.lock.yaml, in the configuration repository, records what a person decided and the tool must not reconsider: accepted and rejected links, merged and separated twin resources, rejected term… | 0 |
| log in the margin | no definition | “…written, the same checks in the merge request and in the build, a SARIF log in the margin of the diff; the wiki keeps pace with the tool, every check having its…” — Roadmap outline | 3 |
| logo | no definition | “The need: an integrator wants the organisation's name, logo, colours and a label here and there, and never wants to touch the components. theme.yaml already car…” — Theme override model | 8 |
| logo, favicon, font | no definition | “2 · WHAT EXISTS theme.yaml Name, logo, favicon, font families, corner radius. Light and dark palettes, checked for contrast at build. Footer text, footer li…” — Theme override model | 3 |
| logo, favicon, font families | no definition | “2 · WHAT EXISTS theme.yaml Name, logo, favicon, font families, corner radius. Light and dark palettes, checked for contrast at build. Footer text, footer li…” — Theme override model | 3 |
| long | no definition | “…nge. A textual equivalent accompanies every graphical view, and a white label installation inherits the guarantees as long as its theme keeps what they rest on.” — Accessibility audit | 3 |
| longest | no definition | “…above, already leads to stays plain text; where two expressions overlap, the longest wins its position. Marking is rendering, and the counts of passages and men…” — Entity page | 3 |
| loops | no definition | “…e Concordance project goes after its first site. Six slides framing the next loops of the tool. A deck, its PDF preview and its notes, grouped by the build in…” — Roadmap outline | 3 |
| lowercase | no definition | “…oot without the extension or the type suffix, slugified segment by segment (lowercase, accents removed, every other run of characters replaced by one hyphen), g…” — Identifier | 2 |
Words without a definition sit in the index like the others, dotted, with the passage that uses them most in place of a definition. That is the working list of a glossary owner.