Skip to content
On this page Definition

Atlas · DS135 · Layout: Narrative

Long-Form Storytelling

Long content split into chapters, data and images.

  • Status in 2026: Established. Documented and in wide use.
  • Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
  • The term: Known technical term or standard.

Definition

Long content split into chapters, data and images.

Traits

  • chapters
  • anchors
  • media

Typical settings: Journalism, Whitepapers.

When to use it, and when not

Consider it when the task and motivation match: people doing deep research. Typical settings: journalism, whitepapers.

Be careful when the risk below would hurt the main task: fatigue and difficulty finding places.

UX risk and how to reduce it

Risk: Fatigue and difficulty finding places.

Mitigation and accessibility: Summary, table of contents and progress.

How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.

Evidence

Indirect: the sources support underlying principles, not a preference for this style.

The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.

Heuristic scales

Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.

Visual complexity heuristic
3 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
3 / 5 (1 is restrained, neutral, 5 is highly expressive)
Information density heuristic
3 / 5 (1 is sparse, 5 is dense)

In our library

No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.

Prompt for your AI

Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.

Design this interface in the "Long-Form Storytelling" direction (layout, narrative): Long content split into chapters, data and images.
Visual and interaction traits to use: chapters, anchors, media.
Main UX risk: Fatigue and difficulty finding places. Mitigate it: Summary, table of contents and progress.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.

References

  1. W3C Web Accessibility Initiative (2021). WCAG 2 supplemental guidance. W3C WAI.Standard or guideline

    Supports: W3C WAI lists supplemental guidance for improving accessibility beyond what WCAG 2 requires, including a cognitive accessibility guidance set.

    Does not support: Normative requirements: supplemental guidance is advisory, not required for conformance. This page is an index; a specific recommendation needs the linked document.

    Checked 2026-10-25.

  2. Wagemans, Elder, Kubovy, Palmer, Peterson, Singh, von der Heydt (2012). A century of Gestalt psychology in visual perception: I. Perceptual grouping and figure-ground organization. Psychological Bulletin, 138(6).Established

    Supports: A review of the grouping principles (proximity, similarity, common fate and others) and of figure-ground organization in contemporary perception research.

    Does not support: Any claim about interface styles. It is a review of perception, not of screens, and says nothing about preference.

    Checked 2026-10-25.