Decision: expanded field set (`photo`, `checklist`) + `showIf` #6

New issue

Closed

opened 2026-07-23 14:46:23 +02:00 by cloudbot · 1 comment

cloudbot commented

2026-07-23 14:46:23 +02:00

Collaborator

Decision — confirm the expanded field set (9 types) and showIf are in v1 scope.

The design doc §5 originally defined 7 field types. The committed prototype ships 9 — it adds photo and checklist — plus a showIf conditional-visibility mechanism. Confirming these are in scope matters because each widens the template parser, and photo pulls in the whole Outline attachment pipeline.

The full 9 types (as rendered in the prototype)

Type	Control
`string`	single-line text input
`multiline`	textarea, 3 rows
`number`	numeric input
`date`	native date input
`time`	native time input
`dropdown`	select, options from config
`checkbox`	pill toggle + hint text
`photo`	image slot, capture/upload an Outline attachment
`checklist`	rows of `[✓] text ✕` + "Add an item"

`showIf`

A field is hidden unless another field is truthy (e.g. show dosage only if prescription is checked). The prototype treats conditional visibility as a first-class feature.

What to decide

Are all 9 types in v1 (vs shipping the original 7 and deferring photo/checklist)?
Is showIf in v1?

Note the coupling: photo cannot ship without the attachment mechanics in #11, and its output is what feeds the Person Info thumbnails in #9.

Related: the Log-button icon for each template comes from the ## App Config icon key (an emoji), not the template's native Outline doc icon — the doc icon can be a custom image (UUID, separate resolution path; see #9) and is often unset. Locked in #2.

Blocks: the template parser and field renderers; photo additionally blocks on #11.

Recommendation: keep all 9 types + showIf in v1 — the prototype already designs and renders them, so the UX cost is paid; the only real new work is the attachment pipeline (#11), which is needed for the Person Info sheet regardless. Deferring photo/checklist would mean re-opening finished design.

Source: Solution Design — Family App v1 §5 (doc vpBNbG4TsV); prototype design/Family App.dc.html; skills/design-system/SKILL.md (Field types).

**Decision — confirm the expanded field set (9 types) and `showIf` are in v1 scope.** The design doc §5 originally defined **7** field types. The committed prototype ships **9** — it adds `photo` and `checklist` — plus a `showIf` conditional-visibility mechanism. Confirming these are in scope matters because each widens the template parser, and `photo` pulls in the whole Outline attachment pipeline. ### The full 9 types (as rendered in the prototype) | Type | Control | |------|---------| | `string` | single-line text input | | `multiline` | textarea, 3 rows | | `number` | numeric input | | `date` | native date input | | `time` | native time input | | `dropdown` | select, options from config | | `checkbox` | pill toggle + hint text | | **`photo`** | image slot, capture/upload an **Outline attachment** | | **`checklist`** | rows of `[✓] text ✕` + "Add an item" | ### `showIf` A field is hidden unless another field is truthy (e.g. show `dosage` only if `prescription` is checked). The prototype treats conditional visibility as a first-class feature. ### What to decide 1. Are all 9 types in v1 (vs shipping the original 7 and deferring `photo`/`checklist`)? 2. Is `showIf` in v1? Note the coupling: `photo` cannot ship without the attachment mechanics in **#11**, and its output is what feeds the Person Info thumbnails in **#9**. Related: the **Log-button icon** for each template comes from the `## App Config` `icon` key (an emoji), **not** the template's native Outline doc icon — the doc icon can be a custom image (UUID, separate resolution path; see #9) and is often unset. Locked in #2. **Blocks:** the template parser and field renderers; `photo` additionally blocks on #11. **Recommendation:** keep all 9 types + `showIf` in v1 — the prototype already designs and renders them, so the UX cost is paid; the only real new work is the attachment pipeline (#11), which is needed for the Person Info sheet regardless. Deferring `photo`/`checklist` would mean re-opening finished design. **Source:** Solution Design — Family App v1 §5 ([doc vpBNbG4TsV](https://outline.marquezkeenan.family/doc/solution-design-family-app-v1-vpBNbG4TsV)); prototype `design/Family App.dc.html`; `skills/design-system/SKILL.md` (Field types).

cloudbot added this to the M0 · Open Questions & Decisions milestone

2026-07-23 14:46:23 +02:00

cloudbot added the

spike

label

2026-07-23 14:46:23 +02:00

cloudbot added a new dependency

2026-07-23 14:46:42 +02:00

#24 Template fetch + parser

cloudbot added a new dependency

2026-07-23 14:46:46 +02:00

#34 Field renderers (9 types + showIf + read-only)