Updates

Changelog

Track Urban Broccoli's evolution with structured release notes, feature updates, and system improvements.

March 2026

v1.1.0

Enterprise Dashboard Components

🚀

Enterprise Dashboard Components

Added comprehensive dashboard components including StatCard, DataTable, and EmptyState with conditional rendering support.

🚀

Changelog Content Collection

Implemented Astro content collection for changelog with structured versioning and change categorization.

🔧

Homepage Redesign

Complete homepage restructure with 9-section layout, pricing tiers, and integration-ready messaging.

🚀

Pro Dashboard Pack

Introduced enterprise-grade dashboard patterns for analytics-heavy interfaces and team management modules.

January 2026

v1.0.0

Initial Release

🚀

Initial Release

Launch of Urban Broccoli as a rebrandable SaaS framework with marketing pages, auth layouts, and dashboard foundations.

🚀

Core Component Library

Established design system with Button, Badge, Card, SectionHeader, and other primitive components.

🚀

Layout System

MarketingLayout and DashboardLayout with consistent navigation and responsive design patterns.

🔧

Tailwind Integration

Full Tailwind CSS integration with custom design tokens and utility-first styling approach.

Related resources

Connect updates back to docs and editorial context.

A changelog works best when each milestone can route readers into deeper implementation notes, broader system documentation, or a direct follow-up conversation.

Guide 5 min read

How to rebrand the starter without layout drift

Use the article route for the narrative behind major structural decisions and system constraints.

Read guide

Reference 4 min read

Review the design system docs

Verify shared component and interaction rules before translating changelog notes into new page work.

Open docs

Next step 2 min read

Talk through upcoming rollout priorities

When the update stream turns into delivery planning, move the conversation into contact or pricing.

Contact the team

Next step

Use release notes to support planning, not just reporting.

The changelog should reassure readers that the system is actively maintained, then route them into the deeper documentation or delivery paths that matter next.

Browse resources View pricing