Amadeni

Library

Blocks

Page building blocks made of several components: a data list with a toolbar, an object header with tabs, a send step. Here they are listed with anatomy, rules and reference code, and this is where new ones get proposed.

  • Data list
  • Object header with tabs
  • Master-detail
  • Section and figure row
  • Send step
  • Form in a dialog
  • Mobile app frame

From proposal to registry

A block only becomes part of the library once it has proven itself. Until then the workshop's target version is the reference that rules and agents point to; src/components/blocks stays empty until then.

  1. 1

    Proposal

    A brief with the problem, two occurrences, anatomy and a draft, from us or from a design round.

  2. 2

    Workshop reference

    Built as the target version of a workshop page, referenced by a rule. Agents build from it.

  3. 3

    Proven in a project

    An agent has built the block in a real project, and the designer has reviewed the result.

  4. 4

    In the registry

    As a registry:block under src/components/blocks, pulled into projects via ui-lock.

Catalogue

Data list

Workshop reference

Many entries with search, filters, status and bulk actions. Candidate for the first registry block; modelled on the DataViewSwitcher from billing and controlling.

Anatomy

  1. 1Toolbar: search, filters, export, main action on the right
  2. 2Status segments with counts that also filter
  3. 3Active filters as removable chips
  4. 4Table with column priorities
  5. 5Bulk bar instead of the toolbar on selection
  6. 6An honest end: “25 of 87 · Load more”
  7. 7Narrow: list entries instead of a table
Rules
R11
Reference code
src/app/[locale]/werkstatt/datenliste/soll.tsx
View in the workshop
View in the workshop

Object header with tabs

Workshop reference

Header of a page about a project, a billing area or an asset: one row, one main action, below it the tab row that stays put when scrolling.

Anatomy

  1. 1Back
  2. 2Title and one status
  3. 3One main action, the rest in the ⋯ menu
  4. 4Tab row as ScrollRow, stuck to the top
  5. 5Shrinks to the title when scrolling
Rules
R10
Reference code
src/app/[locale]/werkstatt/objektseite/objekt-kopf.tsx
View in the workshop
View in the workshop

Master-detail

Workshop referenceFrom design round 1

A grouped selection list on the left, the selected entry with exactly one main action on the right. From the first design round, built with SidebarList.

Anatomy

  1. 1Header with count, progress and bulk action
  2. 2SidebarList with groups and counts
  3. 3Detail with the recommendation as a sentence
  4. 4One main action, alternatives in the menu
  5. 5Narrow: list first, then detail with back
Rules
R5R6
Reference code
src/app/[locale]/werkstatt/entscheidungen/soll.tsx
View in the workshop
View in the workshop

Section and figure row

Workshop reference

Calm structure for pages covering several topics: heading plus content without frames around frames, figures as one row instead of a tile grid.

Anatomy

  1. 1Section: heading, optionally one action
  2. 2Content without its own frame
  3. 3Figure row: label, value, optional hint
  4. 4Notes as a tinted Alert
Rules
R12
Reference code
src/app/[locale]/werkstatt/sammelseite/teile.tsx
View in the workshop
View in the workshop

Send step

Workshop referenceFrom design round 1

The last step before something leaves the house: names recipient, contents and redactions, and only sends after consent and a click. From the first design round.

Anatomy

  1. 1Recipient
  2. 2Contents
  3. 3What was changed or redacted
  4. 4Consent
  5. 5Button that names the consequence
  6. 6Reason while the button is disabled
Rules
R7R8R9
Reference code
src/app/[locale]/werkstatt/lange-laeufe/soll.tsx
View in the workshop
View in the workshop

Form in a dialog

Workshop reference

Creating and editing in a dialog: sections, a fixed footer, a confirmation on close, errors at the field and as a summary.

Anatomy

  1. 1Header with title and a short sentence
  2. 2Named sections, required fields first
  3. 3Optional fields collapsed
  4. 4Error summary as an Alert
  5. 5Fixed footer with a named main action
  6. 6Confirmation when closing with input
Rules
R1R3R4
Reference code
src/app/[locale]/werkstatt/dialog-formular/soll.tsx
View in the workshop
View in the workshop

Mobile app frame

Workshop reference

What an application looks like on the phone: compact header, tabs right below, navigation at the bottom, forms as a drawer.

Anatomy

  1. 1Header: back, title, one action
  2. 2Tabs as ScrollRow
  3. 3List entries instead of tables
  4. 4Drawer from the bottom with a fixed save
  5. 5Navigation at the bottom, at most five destinations
Rules
R13
Reference code
src/app/[locale]/werkstatt/mobil/soll.tsx
View in the workshop
View in the workshop

For design rounds

Propose a block

Proposals come as a brief, not as code in this repo. We check it against the projects, build it as a reference in the workshop and record what was adopted and what was not.

  1. 1Name and one sentence on what the block is for
  2. 2Two occurrences from real projects (page, screenshot)
  3. 3Anatomy: the parts in order
  4. 4States: empty, loading, error, narrow
  5. 5Draft as a link or screenshots, light and dark
  6. 6At most three rules with reasons
  7. 7Which components are missing for it (wish list)

The template to copy is in docs/bloecke.md.

There are no open proposals right now.