{
  "schemaVersion": 1,
  "date": "2026-10-29",
  "task": "Import progress: a loader for a file tool that shows named stages, lets someone cancel and ends with a clear completion state.",
  "request": {
    "repository": "isas1/web-components",
    "number": 45,
    "url": "https://github.com/isas1/web-components/issues/45",
    "title": "Loader tile variety pack (library content)",
    "task": "Import progress: a loader for a file tool that shows named stages, lets someone cancel and ends with a clear completion state.",
    "votes": 0
  },
  "sources": [
    {
      "source": "smashing",
      "status": "fetched",
      "count": 9
    },
    {
      "source": "hacker-news",
      "status": "fetched",
      "count": 20
    },
    {
      "source": "codrops",
      "status": "disabled",
      "reason": "2026-10-27: endpoint returns HTTP 410; awaiting verified replacement"
    }
  ],
  "candidates": [
    {
      "id": "request-isas1/web-components-45",
      "kind": "request",
      "task": "Import progress: a loader for a file tool that shows named stages, lets someone cancel and ends with a clear completion state.",
      "url": "https://github.com/isas1/web-components/issues/45"
    },
    {
      "id": "c15c1be0aad75fb41fbdb15d",
      "title": "Embracing Playful Imperfection With The CSS `random()` Function",
      "url": "https://smashingmagazine.com/2026/10/embracing-playful-imperfection-css-random-function/",
      "source": "Smashing Magazine",
      "sourceId": "smashing",
      "published": "2026-10-20T10:00:00.000Z",
      "summary": "Design systems thrive on consistency, so where does randomness fit in? Through playful demos of organic typography, bouncing letters, and splayed cards, Brecht De Ruyte shows how the new CSS `random()` function brings a little imperfection to the web without JavaScript libraries or preprocessor loops that generate hundreds of lines of static CSS.",
      "kind": "feed"
    },
    {
      "id": "906c26c75ab309095d956d6f",
      "title": "A Practical Guide To Naming Things",
      "url": "https://smashingmagazine.com/2026/10/how-name-things/",
      "source": "Smashing Magazine",
      "sourceId": "smashing",
      "published": "2026-10-06T10:00:00.000Z",
      "summary": "A practical guide to naming UI components, with useful resources, naming conventions, and structures. You’ll find more [useful guides](https://www.smashingmagazine.com/category/guides/) and [online workshops](https://smashingconf.com/online-workshops) here on Smashing Magazine, so make sure to browse and explore.",
      "kind": "feed"
    },
    {
      "id": "b008f772ace718d60f01070e",
      "title": "Building A UX ROI Case That Survives The Boardroom",
      "url": "https://smashingmagazine.com/2026/09/building-ux-roi-case-survives-boardroom/",
      "source": "Smashing Magazine",
      "sourceId": "smashing",
      "published": "2026-09-11T13:00:00.000Z",
      "summary": "Strong UX ideas do not secure investment on their own. Through a worked example, Alex Williams breaks down how to define business value, calculate costs, test causality, and build a credible case for the return on a design initiative. - UX - Design - Business",
      "kind": "feed"
    },
    {
      "id": "8f216ec363408e7c0935b0dd",
      "title": "The Death Of The Button: Why The Best Interface Is No Interface",
      "url": "https://smashingmagazine.com/2026/09/death-button-why-best-interface-is-no-interface/",
      "source": "Smashing Magazine",
      "sourceId": "smashing",
      "published": "2026-09-09T10:00:00.000Z",
      "summary": "The web is evolving beyond menus, forms, and endless clicks toward experiences shaped around human intent. For UX designers, understanding this shift means re-evaluating their role, moving from designing visible interfaces to guiding transparent, intent-driven AI experiences.",
      "kind": "feed"
    },
    {
      "id": "daily-task",
      "kind": "task",
      "task": "Import progress: a loader for a file tool that shows named stages, lets someone cancel and ends with a clear completion state."
    }
  ],
  "recent": [
    {
      "date": "2026-10-03",
      "task": "Running pace calculator: distance and time give pace per km and per mile and projected times for 5 km, 10 km, half, and full marathon.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-04",
      "task": "Weekly planner page with priorities, appointments, and notes, printable on A4.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-05",
      "task": "CV checklist: 15 checks with a score, printable.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-06",
      "task": "Water tracker: a daily goal the user sets and a tap-to-add log that resets each day.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-07",
      "task": "Stretch sequence timer: the user lists stretches and hold times, and the timer runs through them.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-08",
      "task": "Weekly workout planner: days, exercises, sets, and reps, printable.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-09",
      "task": "Goal tracker: one goal with milestones, dates, and percent done.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-10",
      "task": "Camping checklist grouped by shelter, cooking, clothing, and safety, printable.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-11",
      "task": "Daily routine builder: morning and evening steps with times, printable.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-12",
      "task": "Output style: a Claude Code voice that changes how every answer sounds.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-13",
      "task": "Plugin: a bundle of Claude Code mods that arrives like a traveller with a full pack.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-14",
      "task": "Long task: a Claude Code job that runs for hours while no one watches.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-15",
      "task": "Loop: Claude Code waking on a schedule to check on something again and again.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-16",
      "task": "Session log: the trail a Claude Code session leaves behind it.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-17",
      "task": "Mod workshop: a place to build a Claude Code mod from parts.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-18",
      "task": "Companion: a Claude Code mod that keeps someone company while they work.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-19",
      "task": "Scroll progress: a thin line that shows how much of a page is read.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-20",
      "task": "Undo in rewind: a mistake runs back along its own path, the way tape plays in reverse.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-21",
      "task": "Color swatch in dye bath: dip the cloth, and it slowly takes one color from a small set of vats.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-22",
      "task": "Badge in droplets: the count grows as drops merge, and a drop splits off when it goes down.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-23",
      "task": "File drop in a well: a dropped file falls, rings spread, and the echo confirms it arrived.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-24",
      "task": "Empty state in tide pool: an empty list is a still pool with one small creature waiting.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-25",
      "task": "Breadcrumb in footprints: the trail back up is a line of prints that deepen as each is reached.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-26",
      "task": "Log viewer: a compact panel for a developer tool that filters sample events by severity and opens the selected event details.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-27",
      "task": "Pipeline panel: a status panel for a build tool that expands a failed step, shows its log and retries it in a local demo.",
      "components": [],
      "usedSources": []
    },
    {
      "date": "2026-10-28",
      "task": "Latency chart: a chart card for a service dashboard that selects a time range and reveals request latency at a chosen point.",
      "components": [
        {
          "row": 1,
          "id": "range-selector",
          "file": "artifact-1.html",
          "name": "Range selector",
          "description": "Segmented radio group for 1h, 6h, 24h and 7d with fixed label widths.",
          "category": "Inputs",
          "tags": [
            "time-range",
            "radio-group",
            "segmented",
            "dashboard",
            "dedupe"
          ],
          "purpose": "Choose the time window the card reads.",
          "use": "Engineer widens from 6h to 24h to see whether a spike repeats daily.",
          "input": "Click or tap a segment. Keyboard: Tab into the group, arrow keys move and select, Home and End jump to the ends.",
          "outcome": "Range commits and emits one load request. Selecting the active range emits nothing.",
          "recovery": "If the load is cancelled or fails, the selection reverts to the last range that loaded.",
          "mechanism": "Native radio inputs styled as segments. A generation counter tags each request. Older generations are ignored on arrival.",
          "nearestAnalogue": "2026-10-26 log viewer severity filter. That filter narrows a list. This control replaces the whole data window and must abort prior work.",
          "usefulness": "Every latency question starts with a window. Without dedupe, rapid clicks queue several loads.",
          "creativeDifference": "Revert-on-cancel keeps control and chart in agreement, which a plain segmented control does not handle.",
          "states": [
            "idle: one range checked, reached on load",
            "focus: visible ring on checked segment, reached by Tab",
            "pending: checked segment shows a 2px underline while its load runs, reached by selecting a new range",
            "reverted: previous range re-checked with status text 'Kept 6h', reached by cancel or failure",
            "no-op: active range pressed again, nothing changes"
          ],
          "sources": [
            {
              "title": "Engineering-leaning charts and UI components (visitor request)",
              "url": "https://github.com/isas1/web-components/issues/127"
            },
            {
              "title": "ARIA Authoring Practices: Radio Group",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        },
        {
          "row": 2,
          "id": "load-stages",
          "file": "artifact-2.html",
          "name": "Load stages",
          "description": "Status line that names three load stages, allows cancel and ends in a clear complete or failed state.",
          "category": "Feedback",
          "tags": [
            "loader",
            "stages",
            "cancel",
            "retry",
            "status",
            "live-region"
          ],
          "purpose": "Show what the card is doing while data loads, and how it ended.",
          "use": "Engineer sees 'Aggregating 864 samples' and decides to wait or cancel.",
          "input": "Click or tap Cancel or Retry. Keyboard: Tab to the button, Enter or Space.",
          "outcome": "Stages Fetch, Aggregate and Draw tick in order. Completion reads 'Loaded 24h · 288 points · 14:52'.",
          "recovery": "Cancel keeps the previous chart. Failure names the stage that failed and offers one Retry that disables while pending.",
          "mechanism": "A single job object with an AbortController and stage index. Starting a job aborts the current one. Status text sits in a polite live region. No percentage is shown, because stage count is the honest measure.",
          "nearestAnalogue": "2026-10-27 pipeline panel retry. That panel retries a build step. This one reports a data load with cancel and never shows invented progress.",
          "usefulness": "Engineers need to know whether a flat line means low latency or no data yet.",
          "creativeDifference": "Named stages with sample counts replace a spinner, so the wait carries information.",
          "states": [
            "idle: hidden status, reached when no load is running",
            "fetching: 'Fetching 24h', reached by range change",
            "aggregating: 'Aggregating 864 samples', reached after fetch resolves",
            "drawing: 'Drawing p99', reached after aggregate",
            "complete: summary line with timestamp, reached after draw",
            "cancelled: 'Cancelled · kept 6h', reached by Cancel",
            "failed: 'Aggregate failed · kept 6h' with Retry, reached by demo failure toggle",
            "reduced-motion: stage ticks without transition"
          ],
          "sources": [
            {
              "title": "Engineering-leaning charts and UI components (visitor request)",
              "url": "https://github.com/isas1/web-components/issues/127"
            },
            {
              "title": "ARIA Authoring Practices patterns",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        },
        {
          "row": 3,
          "id": "percentile-tiles",
          "file": "artifact-3.html",
          "name": "Percentile tiles",
          "description": "Four tiles for p50, p95, p99 and error rate. The selected tile expands while neighbours yield track space.",
          "category": "Layout",
          "tags": [
            "bento",
            "metric-tiles",
            "percentile",
            "grid-tracks",
            "spring",
            "container-query"
          ],
          "purpose": "Pick which series the chart plots and show current values for all four.",
          "use": "Engineer switches from p99 to p50 to check whether the median moved too.",
          "input": "Click or tap a tile. Keyboard: Tab to a tile, Enter or Space selects.",
          "outcome": "Selected tile expands to show its detail. The chart redraws in that series.",
          "recovery": "Selecting another tile reverses the change. Nothing is lost.",
          "mechanism": "rAF loop eases CSS fr track variables with k = 1 - (1 - 0.14)^dt, dt capped at 50 ms. The loop stops when the summed error drops below 0.002. Below 480 px container width, tiles become a chip row with no track animation.",
          "nearestAnalogue": "None in recent dates. Source c16 magnetic bento is the direct ancestor.",
          "usefulness": "Percentile choice changes what a spike means. Current values for all four stay visible.",
          "creativeDifference": "Track yielding ties layout to selection, while values stay readable during resize.",
          "states": [
            "default: p99 selected, reached on load",
            "selected: expanded track with detail and accent border, reached by click or Enter",
            "focus: outline ring, reached by Tab",
            "settled: loop stopped, reached about 400 ms after selection",
            "compact: chip row under 480 px container width",
            "reduced-motion: tracks set directly"
          ],
          "sources": [
            {
              "title": "c16 magnetic bento (creative-sites-vault)",
              "url": "https://github.com/isas1/creative-sites-vault/blob/1595af38a69fbb67c674ef4b90b776a2245c270b/00-components/cards/c16-magnetic-bento.html"
            },
            {
              "title": "Stop Treating CSS Container Queries Like Traditional Media Queries",
              "url": "https://smashingmagazine.com/2026/09/stop-treating-css-container-queries-traditional-media-queries/"
            },
            {
              "title": "ARIA Authoring Practices: Button",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        },
        {
          "row": 4,
          "id": "cursor-chart",
          "file": "artifact-4.html",
          "name": "Cursor chart",
          "description": "SVG line chart with an SLO line and a cursor that snaps to measured samples and reveals the value at that point.",
          "category": "Data",
          "tags": [
            "line-chart",
            "crosshair",
            "latency",
            "slo",
            "svg",
            "keyboard-chart"
          ],
          "purpose": "Reveal request latency at a chosen point.",
          "use": "Engineer drags across the deploy and reads '14:35 · p99 640 ms · +340 over SLO'.",
          "input": "Pointer move or touch drag over the plot. Keyboard: focus the plot, Left and Right step one sample, Page Up and Page Down step 12, Home and End jump to the ends.",
          "outcome": "Readout above the plot shows time, value and offset from SLO. Cursor snaps to the nearest real sample.",
          "recovery": "Escape returns the cursor to the worst breach. Leaving the plot keeps the last cursor position.",
          "mechanism": "Nearest-index lookup from x position against sample timestamps. Readout has fixed width from the longest sample label. Plot is a focusable element with role group and an aria-live readout.",
          "nearestAnalogue": "None in recent dates. 2026-10-19 scroll progress maps position to value in one dimension, with no data points.",
          "usefulness": "This component answers the core need. Snapping prevents reading interpolated values that were never measured.",
          "creativeDifference": "The readout states distance from SLO, which reframes the number as a decision.",
          "states": [
            "initial: cursor on worst breach, reached on load",
            "tracking: cursor follows pointer, reached by pointer or touch",
            "focus: plot outline and key hint, reached by Tab",
            "breach: readout marked over SLO, reached when value exceeds 300 ms",
            "stale: dimmed plot while a new range loads",
            "empty: 'No samples in range', reached when a range returns zero points"
          ],
          "sources": [
            {
              "title": "Engineering-leaning charts and UI components (visitor request)",
              "url": "https://github.com/isas1/web-components/issues/127"
            },
            {
              "title": "ARIA Authoring Practices patterns",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        },
        {
          "row": 5,
          "id": "breach-stepper",
          "file": "artifact-5.html",
          "name": "Breach stepper",
          "description": "Previous and next controls that move the chart cursor between SLO breaches, with a count.",
          "category": "Navigation",
          "tags": [
            "stepper",
            "breach",
            "slo",
            "pager",
            "jump"
          ],
          "purpose": "Move directly between moments where latency crossed the SLO.",
          "use": "Engineer steps 'Breach 2 of 4' to 'Breach 3 of 4' to see whether the second spike followed a deploy.",
          "input": "Click or tap Previous or Next. Keyboard: Tab to the buttons, Enter or Space. Held keys move one step per keydown.",
          "outcome": "Cursor jumps to the peak sample of the next breach. Count updates.",
          "recovery": "The buttons disable at the ends, and the count reads 'Breach 4 of 4'. Escape in the chart returns to the worst breach.",
          "mechanism": "Breaches are contiguous runs above SLO, computed once per load. Each run is stored by its peak index. A step sets the cursor index directly and replaces any running transition.",
          "nearestAnalogue": "2026-10-25 breadcrumb in footprints moves through a path. This moves through computed events in data.",
          "usefulness": "Finding breaches by dragging across 288 points is slow on a phone.",
          "creativeDifference": "Navigation targets come from the data itself, not from pages or sections.",
          "states": [
            "default: 'Breach 1 of 4', reached on load",
            "middle: both buttons enabled",
            "start or end: one button disabled with count at bound",
            "none: 'No breaches in 1h' with both disabled, reached when range has none",
            "focus: visible ring"
          ],
          "sources": [
            {
              "title": "Engineering-leaning charts and UI components (visitor request)",
              "url": "https://github.com/isas1/web-components/issues/127"
            },
            {
              "title": "ARIA Authoring Practices patterns",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        },
        {
          "row": 6,
          "id": "pin-pair",
          "file": "artifact-6.html",
          "name": "Pin pair",
          "description": "Button that pins the cursor point. Two pins produce a delta line.",
          "category": "Actions",
          "tags": [
            "pin",
            "compare",
            "delta",
            "button",
            "dedupe"
          ],
          "purpose": "Keep two moments and compare them.",
          "use": "Engineer pins 14:15 and 14:35 and reads '+412 ms p99 over 20 min'.",
          "input": "Click or tap Pin. Keyboard: Tab to Pin, Enter or Space. P while the chart has focus. Each pin chip has a remove button.",
          "outcome": "First pin shows a marker. Second pin shows the delta line. A third pin replaces the oldest.",
          "recovery": "Remove any pin with its x button or Delete on the focused chip. Pinning an already pinned point does nothing.",
          "mechanism": "A two-slot array keyed by sample index. The label swaps in a reserved width: Pin, Pinned, Replace oldest.",
          "nearestAnalogue": "2026-10-20 undo in rewind deals with reversal of an action. This keeps two references and computes between them.",
          "usefulness": "Before and after a deploy is the comparison on-call engineers report.",
          "creativeDifference": "The delta is the action's result, so no separate compare panel is needed.",
          "states": [
            "empty: 'Pin this point'",
            "one pinned: marker on chart, label 'Pin second point'",
            "pair: delta line shown",
            "full: label 'Replace oldest'",
            "duplicate: label 'Already pinned', no change",
            "cleared: pins removed on range change, with status note"
          ],
          "sources": [
            {
              "title": "Engineering-leaning charts and UI components (visitor request)",
              "url": "https://github.com/isas1/web-components/issues/127"
            },
            {
              "title": "ARIA Authoring Practices: Button",
              "url": "https://www.w3.org/WAI/ARIA/apg/patterns/"
            }
          ]
        }
      ],
      "usedSources": [
        "5c9d13f97faabce46da9b702"
      ]
    }
  ],
  "inventory": null
}
