Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Experiment Calendar Block for Solid

Six tests as lanes on a six-week calendar with progress to today, the next significance check and a hatched stretch where two tests share a surface, with a choice of lane that reads its arms and sample.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

See what is running, what is scheduled and which tests are stepping on each other, with this experiment calendar for Solid with Ark UI. It is Trialbench, an experimentation platform (made up), showing six tests as lanes on six weeks from 28 September to 8 November. Each lane has a bar from the test's start to its planned end, filled up to the snapshot day, a diamond on the day of its next significance check, and a hatched stretch with an outlined chip where another test is on the same surface at the same time. The lanes are one radio group: choosing one reads its arms and the visitors so far and lists its dates in a row of figures. The header counts the running and scheduled tests and the crowded surfaces, worked out from the dates. Guides draw the frame and its bands; the entrance is CSS only. For growth and product teams who run several tests on one product.

FAQ

How do I use my own tests?

Edit TRIALS: each has a surface, start, end and check counted in days from the first day on the calendar (FIRST_DAY), visitors a day in perDay, and its arms with their shares. NOW is the snapshot day. Overlaps, the visitors so far, the header counts and the chips are derived from the dates.

What counts as an overlap?

Two tests on the same surface whose date ranges share at least one day, including a test that is scheduled but has not started. The stretch they share is hatched in each lane, and the chip names the other test (and how many more). Tests on different surfaces never overlap, even on the same days.

How does it work on a phone?

The calendar needs about 40rem, so it scrolls sideways inside a named region while the lane names stay in view. The lanes are still radios, so a keyboard moves between them with the arrow keys, and the figures under the calendar do not scroll.

What stays local?

All of it. No test runs, and the dates and visitor counts are typed examples. To make it real, read tests from your experimentation tool and keep the calendar, the overlap rule and the figures.

Can I read it without colour?

Yes. Progress is a solid fill against an outline, the check is a diamond, the overlap is hatched with a text chip, and every lane has an accessible name with its dates, state and overlap.

How is this different from the A/B comments block?

That one is a live experiment on a comment box. This one is the calendar of many tests and the places they collide, and it does not ask which variant won.