Files
bible/rules/patterns/timeline-views/contract.md
T

1.8 KiB

Contract: Timeline Views

Version: 1.0

Scope

An optional Gantt view for dates and parent/child records already represented by an operator table. Visual styling inherits web-visual-baseline; filters inherit table-management. This pattern comes from stok's active List/Gantt workflow. It does not require a calendar view.

Rules

  • Keep the list as the default view. Use a compact joined List/Gantt switcher and retain the active filters when switching. Persist view/range in URL state when the page is shareable.
  • Use ISO weeks for planning, with a visible range title and previous/current/next controls. Mark the current week; include the ISO year wherever week numbers would be ambiguous.
  • Use a bounded scrolling surface, a sticky week header and a sticky name column. Keep filter popups above it and outside clipping ancestors using the shared dropdown mechanism.
  • Parent names expand/collapse meaningful child detail. Timeline bars open the corresponding record editor. These actions must not trigger each other; both work with the keyboard.
  • Keep bar labels concise (identity/quantity), with complete dates/status available on inspection and through an accessible name. Short bars must not make their labels unreadable; labels may overflow within a lane if they do not cover another control.
  • Display server-supplied status with text/shape as well as color. Distinguish actual-date markers from planned spans and open-ended spans from completed ones.
  • Reuse the same records and filters as the list; do not create separate business calculations for the chart. Missing dates must not silently become today's date or disappear without an unscheduled indication or an explicit count/link back to the list.

See examples for geometry and the source decisions.