Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Content Calendar Task List Block for Solid

A content plan read by publishing week, with this week, next week and later bands, a type filter, per-week totals of pieces and words to write, and an Advance button that steps each piece from Draft to Published.

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

Plan what goes out and when without a month grid, with this content calendar to-do list block for Solid with Ark UI. Eleven pieces (blog posts, newsletters, videos and social posts) sit in three bands worked out from each piece's publish date against a fixed today: this week, next week and later. A Toggle Group at the top filters every band by type, and each band's heading counts its pieces and the words still to write. Every piece has an Advance button that steps its stage from Draft to In review, Scheduled and Published, shown as a word and a glyph and never a colour, and the totals follow. The bands hold their height while you filter. Guides rule the bands. For editorial teams, newsletters and anyone who plans content a week at a time.

FAQ

How are the weeks decided?

This week runs Monday 12 to Sunday 18 October, around a fixed today of Wednesday 14. A piece's publish date puts it in the band: the same week, the week after, or anything later. Nothing is typed in as a label.

What do the totals count?

Pieces and the words of pieces that are still a draft, for what the current filter shows. Moving a piece to In review counts its words as written, so the band's figure drops.

What does Advance do?

It moves one piece one stage, never backwards or past Published. At Published the button stays focusable and answers that the piece is already out instead of doing nothing.

Why does nothing jump when I filter?

Each band lays the full set of its pieces out unseen under the filtered list, so the band keeps its height. A band with nothing of the chosen type says so in a line.

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

The pieces and their stages live in the page and reset on reload. In an app, store a stage and a publish date per piece, and write from advance; the bands and totals can stay derived as they are here.

How does it look on a phone?

The type filter scrolls sideways inside its own row, each piece keeps its title, its details and its stage on three short lines with Advance at the end, and the band totals wrap under the band name.