Follow our journey as we build. Here are the latest updates from our engineering team.
Beta program opens to first 500 users
Added real-time collaboration with cursor presence
Resolved edge case in OAuth token refresh flow
Reduced API response time by 40% with query optimization
Refactored notification service to support webhooks
Implemented dark mode across all dashboard views
Fixed timezone handling in scheduled reports
Coming soon section with a chronological development log feed showing recent updates, commits, and milestones. Perfect for building in public and keeping the community engaged.
A centered coming-soon section that stacks a badge, heading, and description above a chronological log feed, where each entry pairs a type-colored icon with a message, a type pill, an optional author, and a date across a divider-separated list.
Upgrade to Pro
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://ui.beste.co/r/comingsoon10?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/comingsoon10?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/comingsoon10.tsx.
The installed file exports comingsoon10Demo alongside the block: the exact props behind the preview above. Spread it to get a working dev log feed in one line.
import { ComingSoon10, comingsoon10Demo } from "@/components/beste/block/comingsoon10";
export default function Page() {
return <ComingSoon10 {...comingsoon10Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { ComingSoon10 } from "@/components/beste/block/comingsoon10";
export default function Page() {
return (
<ComingSoon10
badge={{ label: "Building in public", variant: "secondary" }}
heading="Development log"
description="Follow our journey as we build, with the latest updates from the team."
entries={[
{
type: "milestone",
message: "Beta program opens to first 500 users",
date: "Mar 18",
author: "Team",
},
{
type: "feature",
message: "Added real-time collaboration with cursor presence",
date: "Mar 15",
author: "Sarah",
},
{
type: "fix",
message: "Resolved edge case in OAuth token refresh flow",
date: "Mar 14",
},
]}
labels={{
feature: "Feature",
fix: "Fix",
improvement: "Improvement",
milestone: "Milestone",
commit: "Commit",
}}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
badge | { label: string; variant?: "default" | "secondary" | "outline" } | – | Eyebrow badge rendered above the heading via shadcn Badge |
heading | string | – | Section heading |
description | string | – | Supporting paragraph under the heading |
entries | LogEntry[] | [] | Chronological log entries |
labels | { feature?: string; fix?: string; improvement?: string; milestone?: string; commit?: string } | – | Type-pill text for each log type |
className | string | – | Extra classes for the outer <section> |
type LogType = "feature" | "fix" | "improvement" | "milestone" | "commit";
interface LogEntry {
type: LogType;
message: string;
date: string;
author?: string;
}logTypeConfig record keyed by its type to pick the icon (Sparkles, Bug, CheckCircle2, Rocket, or Code2), its icon color, and the matching pill color classes.getTypeLabel, which maps each type to the matching labels string with "Feature", "Fix", "Improvement", "Milestone", and "Commit" fallbacks.entries.length > 0; each row draws a bottom border-b divider except the last, computed from index !== entries.length - 1.author span renders only when an entry supplies one, sitting beside the type pill, while the date is pinned to the right of each row.Badge primitive for the eyebrow and lucide icons for the per-entry types.comingsoon2
Coming soon section with a progress bar and milestone tracker showing development stages like Design, Backend, Frontend, and Testing. Perfect for keeping users informed about product development progress.
comingsoon7
Coming soon section with a vertical timeline showing launch phases, dates, and status indicators. Perfect for communicating a clear release plan and keeping users informed about upcoming milestones.
comingsoon9
Coming soon section with a bento-grid of live build stats like commits, test coverage, uptime, and team size. Perfect for building in public with transparent engineering metrics.
comingsoon78
A pre-launch section that publishes remaining work instead of a date, with an image tile floating a live release tracker over hairline rows marked shipped, in testing, or queued.