Blocks and patterns
Whole screens and the parts they are made of: the app shell, a list page, a detail page, the data table, the detail sheet and the board. Start a new app from these and change what your team needs.
The frame of a Waimakers app: a sidebar with the product lockup, navigation and the signed-in colleague, a top bar with the breadcrumb, and room for the page. Pages own their own heading.
A list page in one block: the page header with its main action, a toolbar for search and filters, and a responsive table whose rows open in a detail sheet. Each row ends in an Inspect action, and the sheet keeps the identifier under technical details.
A detail page in one block: breadcrumb, title with status and actions, sections of labelled facts, and the technical details folded away until someone needs them.
The list every Waimakers app ends up needing: sort, filter, expand and select rows, with stacked rows on a phone and named states for loading, empty, refused and failed.
Open one record beside the list without leaving it. The header and footer stay put while the body scrolls, and focus returns to the row you came from.
Lanes of cards you move by pointer, touch or keyboard. The board reports each move and your app decides what happens; screen readers hear every pick up, move and drop.