The distributable form (52 passages, no note) of a type: a folder named after the type slug that carries everything the type needs, type.yaml with its declaration (group, glyph, attributes, the sections whose heading produces a relation, the display rules), messages/<locale>.json with the labels of the type, its attributes and its sections (note: Section) per interface language, template.md with its note template, and optionally schema.json for the items of its list attributes and components/ for a page, an attribute value or a section rendered specially. The core types are modules (27 passages, no note) and the default profile is assembled from them; a project (note: Project) keeps its own modules in the folder its profile names under types_dir, and a plugin contributes modules through the types contribution point. The modules are merged before the keys of the project profile, plugins first; a module of a core type is refused, that type being extended through the profile, and two modules of one type are a configuration (note: Configuration) error (29 passages, no note).
Type module
Properties3
- Application
- Concordance command line
- Domain
- Typing and filing
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapType module
Neighbourhood map Type module
Distance1 hop
44 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ProfileTermspecializes2
- NoteTermspecializes1
- AttributeTermspecializes2
- TypeTermspecializes4
- Contribution pointTermspecializes1
- PluginTermspecializes5
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.