The type of a note (3 passages, no note) comes from where it is filed, not from what is written in it. The integrator (note: Integrator) declares the routes once in the configuration (note: Configuration): the type (note: Type) of a whole source (note: Source), a default for what no rule (note: Rule) names, rules on a folder, a file suffix (14 passages, no note), an extension (note: Plugin) or the presence of a frontmatter (note: Frontmatter) key (46 passages, no note), evaluated in order with the last match (note: Occurrence) winning. An author (note: Author) writes a file in the right folder and it is typed; frontmatter (4 passages, no note) is the exception, for the note (note: Note) whose place and type disagree, and it wins. Every entity (note: Entity) records the route that typed (37 passages, no note) it, so that a page can say whether its type came from the source, a rule, a suffix or the note itself, and a type the profile (note: Profile) does not declare is reported rather than guessed.
Type by filing
Decision · Acceptedspecs/notes/type-by-filing
Properties
- Status
- Accepted
- Decided on
2 keys: the status and the date are authoritative.
See the neighbourhood map6 pages6Neighbourhood mapType by filing
Neighbourhood map Type by filing
Distance1 hop
21 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Type conflictBusiness ruleaffects1
- Unknown typeBusiness ruleaffects1
- Build pipelineProcessaffects1
- LintProcessaffects1
- EntityBusiness objectaffects1
- BuildBusiness objectaffects1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.