Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Release Notes Checklist Block for Solid

A release task list that drafts its own Markdown notes from the tasks you tick, with a readiness line against working days to go, a Copy button and a Download notes button that saves a real .md file.

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

Write the notes as you finish the work, with this release notes block for Solid with Ark UI. Ten tasks sit in three bands (New, Fixed, Changed), each a Checkbox for "shipped in this release". A summary band shows On track or At risk by comparing the tasks still open with the working days to go before the target date, with a Progress bar and the rule written out. Below the bands a read-only Textarea holds the draft notes as Markdown, rewritten from only the ticked tasks. A Copy Button puts the text on the clipboard, and the only colored control, a Shine Button named Download notes, saves a real .md file made in the browser. Bands are ruled by Guides. For release managers, changelog drafts and any team that writes notes from a task list.

FAQ

How are the notes drafted?

Each ticked task becomes a bullet under its band's heading, with its area in brackets; a band with nothing ticked is skipped, and with nothing ticked the draft says so. It is a pure function of the task list, so the text and the checkboxes never disagree.

How does Download notes work?

The click builds a Blob of the Markdown, makes a temporary object URL, clicks a hidden link with a file name, and revokes the URL. No server is involved, so the file is created in the visitor's browser.

How is readiness worked out?

Working days (Monday to Friday) from the fixed AS_OF date up to the target are counted once. If the open tasks are no more than those days, at one a day, it says On track; otherwise At risk. The rule is printed in the band so nobody has to guess.

What stays local, and how do I wire it for real?

The ticks and the draft stay on the page and nothing is published. In your app, load the tasks from your tracker, save each tick from toggle, and send the notes to your release page from the Download handler or a separate Publish action.

How does it look on a phone?

The tasks are single-column rows with their area under the title. The draft field keeps ten rows and scrolls inside itself, and Copy and Download notes stay together above it.