MICA / LISTS

One collection. Less chrome.

A list can separate its entries without making every entry a card. Start with the content, add a quiet metadata line, and leave the actions within reach.

Northbridge 2 – 1 RiversideExample fixture · Sample observations, not account data

Notes

One surface, no item boxes. Content and metadata share a row; only entries are separated.

My notes Private

  1. @Jamie Reed kept finding space behind the right back. The early diagonal pass was on more often than we used it.

  2. The press improved after the break. The midfield stepped higher together instead of leaving the striker isolated. Worth comparing the first 15 minutes of each half.

    · Edited

  3. Watch the second-ball positioning on corners.

The same anatomy beyond notes

An optional leading visual, a flexible content area, and optional trailing information or actions. Each row keeps native links and buttons.

Match files

Shared with

  • Jamie Reedjamie@example.com
    Owner
  • Alex Lanealex@example.com

API: native ul/ol[data-list] with li children and optional data-list-leading, data-list-body, data-list-meta, and data-list-trailing parts. Inset dividers separate entries by default. Set data-dividers="none" on an individual list to hide them without changing row spacing. The containing surface owns any outer border; the list adds no hover fill, icon, selection behavior, or row-wide click target.

<ul data-list role="list">…</ul>
<ul data-list data-dividers="none" role="list">…</ul>

Current Mica controlsLink

Delete this note?

This removes the note from this local example.

Preview

Example destination. Your application owns navigation and file access.