Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Social Media Task List Block for Solid

A queue of six posts for three channels in time order, with an editor beside it that shows a live character count against the channel limit, a fixed set of time slots and a Schedule button that says why it is closed.

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 a post to fit its channel and give it a time, with this social media to-do list block for Solid with Ark UI. The queue lists six posts in time order, scheduled ones first and drafts after, each with a two-letter channel tile and its status. Choosing one opens it in the editor: a Textarea with a live count against the channel's limit ("104 of 280", or "Over by 9"), a Native Select of fixed time slots, and a Shine Button that stays closed, and says why, while the text is empty or over the limit or no time is chosen. Scheduling moves the post into the queue at its time, and Move to drafts takes it back. Nothing is ever posted. Guides rule the frame and the split between queue and editor. For makers, small studios and anyone who writes for more than one channel.

FAQ

Where do the limits come from?

Each channel in the data has a character limit: 280 for short notes, 3,000 for essays and 2,200 for stories. The count is the trimmed text length against the limit of the post's channel, and the same post would read differently on another channel.

Why is Schedule never disabled?

It is marked unavailable but stays focusable, so pressing it can explain itself: "Write the post first", "Over the limit: shorten the post" or "Choose a time". A disabled button would give a keyboard or screen reader user no reason.

When does the count get announced?

Only when the post crosses its limit, in either direction, so typing doesn't chatter. The visible count updates on every key.

When does the queue re-order?

When you press Schedule or Move to drafts, not while you type, so a row never moves under your pointer. Scheduled posts sort by their slot and drafts keep their order.

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

The posts, the slots and the queue live in the page and reset on reload, and no channel is contacted. In an app, send the text, channel and time to your scheduler from schedule, and read the limits from each channel's own rules.

How does it look on a phone?

The queue comes first as a short list and the editor stacks under it with the same fields. The count, the time and the buttons stay together, and nothing scrolls sideways at 320 pixels.