A practical pattern atlas
From content meaning to interaction needs.
Use structured Scripture data as a source of scenarios, not as the public navigation of the atlas.
Practical takeaways
- Use content structure to preserve meaning and provenance, not to dictate one fixed layout.
- Resolve edition and reference identity before moving annotations or synchronising panes.
- Test poetry, notes, ranges and enlarged text with representative data.
The same note may appear inline, in a mobile sheet or in a study panel. Its meaning remains stable while the presentation changes with the task and screen.
Preserve the distinctions
The USFM documentation is a technical reference for Scripture structure. It does not cover every app capability, personal annotation model, audio timeline or pastoral requirement. The atlas therefore names user-facing concepts rather than marker codes.
| Content concept | Interaction need | Pattern and source |
|---|---|---|
| Translation addition | Explain words supplied by translators; do not imply AI authorship. | Editorial distinctions survive reflow Translation additions |
| Footnote | Inspect an edition note and return to its text anchor. | Footnotes without losing place Footnote structure |
| Cross reference | Preview and compare a related passage while preserving the origin. | Peek, compare and return Cross-reference structure |
| Poetic paragraph | Preserve relative structure through reflow. | Editorial distinctions survive reflow Poetic paragraphs |
| Study footnote or sidebar | Offer a separate, attributed editorial reading layer. | Content layers have owners Extended study footnotes |
| Internal editorial remark | Retain it in appropriate workflows while keeping it out of publication. | Content layers have owners Internal editorial remarks |
Notes, comments and interpretation
A publisher’s study note, an internal translation remark, a user’s personal annotation and an AI explanation are different objects. Each needs provenance, visibility and rights that match its role. A personal highlight changes an annotation layer, not the licensed Scripture text.
Build a meaningful test corpus
Include multiple note parts and reference groups, translator additions, poetry, continuous paragraphs, study excursions and internal remarks. Add reference numbering differences, missing mappings and unsupported structures. Test reading, copying, search, listening and returning from each interaction with enlarged text and assistive technology.
The resulting UI choices are design proposals. Technical correctness is necessary, but does not establish reading usability.