# Board column

> A kanban column for things people pass between them: a department's requests, notes waiting for an answer.

Source: https://kwark.space/designSystem/components/board-column

## Usage

### When to use
When several people hand items to each other and the only state that matters is *whose move it is*: department requests, notes from a read-through waiting for the writer, deliverables waiting for sign-off.

### When not to
- For story order. Use the [Outline board](https://kwark.space/designSystem/components/outline-board.md), whose columns are the writer's sections.
- For one person's private list. A checklist is calmer.
- Never to grade people's speed, and never with counters of overdue items in red.

### Variants
- **Two to four columns.** More than four means the states are not states but a process; draw it as a list with a status column in a [Data table](https://kwark.space/designSystem/components/data-table.md).
- **Card content**: what (bold, with the scene), who and when in meta text.

### Writing
Column names are states in plain words, past tense where possible: *Asked*, *Answered*, *Agreed*. Never *Backlog*, *WIP* or *Blocked*.

**Do:** *Asked* and *Answered*, each card naming the scene and the department.

**Don't:** Six columns with WIP limits and a red count of overdue cards.

## Style

### Anatomy

Same column as the Outline board: 280px, `--k-raise`, 10px corners, a 2px rule in the column colour, the add control at the foot. Cards are plain [Cards](https://kwark.space/designSystem/components/card.md).

### Tokens

| Token | Light | Dark |
|---|---|---|
| `--k-raise` | #f1f5f9 | #252525 |
| `--k-line` | #e2e8f0 | rgba(255, 255, 255, .1) |
| `--k-radius-card` | 10px |  |
| `--k-cal-reading` | #a87b32 | #dcb36a |
| `--k-cal-rehearsal` | #4f7359 | #86b392 |

## Code

### React

Use the HTML below with `kwark.css`. The example shows the markup and styling. Supply any application behavior described on this page.

### HTML and CSS

Works anywhere with `kwark.css`.

```html
<div class="kw-board">
  <section class="kw-column" style="--kw-act:var(--k-cal-reading)" aria-label="Asked, 2 notes">
    <div class="kw-column__head"><h3>Asked</h3><span class="kw-meta">2</span></div>
    <div class="kw-card"><strong>Scene 12: practical monitor</strong><p class="kw-meta" style="margin:4px 0 0">Art department · asked by Mira</p></div>
    <div class="kw-card"><strong>Scene 14: rain bars</strong><p class="kw-meta" style="margin:4px 0 0">Effects · asked by Arjun</p></div>
  </section>
  <section class="kw-column" style="--kw-act:var(--k-cal-rehearsal)" aria-label="Answered, 1 note">
    <div class="kw-column__head"><h3>Answered</h3><span class="kw-meta">1</span></div>
    <div class="kw-card"><strong>Scene 3: period phone</strong><p class="kw-meta" style="margin:4px 0 0">Props · answered today</p></div>
    <button class="kw-column__add" type="button">Add a note to Answered</button>
  </section>
</div>
```

## Accessibility

- Columns are `<section>`s named with their state and count.
- Every card can change column from a menu, not only by drag; announce the change.
- Colour of the rule is decoration; the state is the column's name.

## For agents

### Rules

- **Never** use more than four columns.
- **Must** name columns as plain states, never process jargon.
- **Always** let a card move by menu as well as drag.
- **Never** show overdue counts or speed metrics about people.

### AI readiness test

**Task:** Track art department requests from the director for Blank Pages.

**Give the agent:** Board column, Card, Sharing by film role.

**Constraint:** Only the art department can move a request to Answered.

**A reliable answer:**
- Two or three columns named as states
- Cards name scene and department
- Move by menu and drag
- Role check before moving
- No overdue counters
