Patterns
How components combine into screens in any Raft product.
- Choosing a componentWhich component to use when people pick something, when you tell them something, for what floats above the page, while they wait, and for a row.
- Page structureThe regions of a phone page and a desktop screen, how they are layered from the frame inward, and the rule of one line between regions.
- NavigationHow people reach destinations, see where they are, follow links, go back, close things, switch workspaces and switch between the views of one place.
- AgentsHow an agent is shown — who it is, its state, the work it is doing, what it finished and what it needs — and where working agents appear.
- TasksThe five task statuses, task lists and boards, task details, how status changes and how tasks are filtered.
- ConversationThe timeline of messages and event lines, what a message can hold, its actions, threads and search in a conversation.
- Forms and settingsSettings that apply at once, forms that are saved, the large one-pass form dialog, validation and the danger zone.
- FeedbackHow to tell people something — undo instead of confirm, empty versus loading versus failed, where errors go by scope, and how they are worded.
- Responsive layoutThe breakpoints, what each width shows, how short desktop windows shrink, and how phone layouts hold at 320px.
- CompositesThings the product needs that are built from existing components instead of having a design of their own — task details, the lightbox, embeds, tables, date picking and more.