Fragment

TermSpace Glossary

The file the build (note: Build) writes next to the model for one entity, under fragments/<id>.json: the note rendered to sanitised HTML, one section per heading, its written links already turned into page links, or the passages of a keyword page. The rendering reads the model and the fragments and nothing else, so concordance render rebuilds the site without cloning a source. A fragment belongs to one entity and never gathers several. An entity another note cites has a second one, fragments/<id>.mentions.json, holding every mention of it; its page carries the first twenty and loads the rest from there.

Properties3

Status
valid

3 declared keys. The rest of the file is free text.

See the neighbourhood map6 pages6Neighbourhood mapFragment

Neighbourhood map Fragment

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

65 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.