Blazor Blueprint, nine months on: what I've learned from my first open source project

Description and use

Blazor Blueprint evolved from a personal component library into a popular open‑source set, accelerating development across multiple projects and earning over 600 GitHub stars.

Problem

Developers wanted a modern, clean UI library for Blazor that matched the style of shadcn/ui but existing options were unsatisfactory.

Outcome

Blazor Blueprint grew from a personal library to a widely used open-source component set, accelerating development in multiple projects and achieving community recognition.

Workflow

• 1. Identify UI style gap in Blazor.
• 2. Build custom components while developing a real product for immediate feedback.
• 3. Release the library as open source on GitHub.
• 4. Iterate based on community and internal usage.
• 5. Add new components (Scheduler, Pivot Grid, charts, etc.) in subsequent releases.

Evidence

I wanted the modern, clean look of shadcn/ui in Blazor, and nothing out there gave me that.

Source

Building it alongside a real product. Every component went straight into real use, so I got instant feedback on what worked and what didn’t.

Source

The project has gone from 160 stars in its first week to over 600.

Source