🚀 Blazor Blueprint - Version 3 Announcement

[mathewtaylor]

🚀 Blazor Blueprint - Version 3 Announcement

Hi everyone,

I wanted to share a quick update on the direction of Blazor Blueprint.

I’ll be releasing Version 3 soon. This update focuses on refining several APIs based on what I’ve learned since the initial announcement, through community feedback, issue reports, discussions, and seeing how the library is being used in real-world projects.

First, thank you.

The positive feedback, thoughtful issue reports, and help testing fixes have made a real difference. It’s been encouraging to see the project gain traction and to have developers actively engaging with it.

Although I’ve been in software development for over 20 years, this is the first time I’ve released something as open source and watched it grow publicly. It’s been both exciting and educational. I wasn’t expecting to reach Version 3 this quickly.

A bit of context:

• v1 was originally released as Blazor UI
• The name conflict required a rename
• That rename introduced namespace changes, which led to v2
• Now, further component refinements will introduce breaking changes, leading to v3

This is not intended to be a frequent pattern. I’m still finding the right balance and refining the design philosophy of the library. Going forward, my intention is to maintain backward compatibility wherever possible and reduce the need for major version increments.

What to Expect in v3

• Several bug fixes identified by the community
• Reduced verbosity in certain components
• APIs more aligned with idiomatic Blazor practices
• Streamlined component patterns for cleaner usage

I’ll share a detailed change log and migration guidance closer to release.

Until then, thank you again for the support, encouragement, and collaboration. It’s been a great experience so far, and I’m looking forward to continuing to improve Blazor Blueprint UI together.

Mathew

[mathewtaylor]

So I have been working hard on the new release and I am thinking about prefixing the component names with Bb, for example BbButton, BbSelect, BbCombobox etc...

My reason for this is two fold:

1. It prevents conflicts with other libraries that are using generic names
2. It prevents conflicts if Microsoft decides to add any components in to the Blazor framework
3. It help identify that the component is from Blazor Blueprint when looking at the source code

Would love to know what the thought of the community is on this?

Note, the next release already contains breaking changes so if I am going to change it, now would be the best time to do it - also while the library adoption is still small (but hopefully growning).

Cheers,
Mathew

[russkyc]

Would you be open to having the prefix be simply 'Ui':

• UiButton
• UiCombobox
• UiDialog
• Others

It doesn't seem like there are other libraries using such as of the moment

[mathewtaylor]

Interesting idea, but I am wondering if using Ui maybe it would not be clear what library it's referring to exactly. I thought Bb makes it clear on that. However, regardless of the prefix, you think the idea of adding a prefix is a good one?

[russkyc]

I'm all in with the prefix, I just thought Ui is also a nice option. Can't wait for V3!

[russkyc]

The community in general would also probably be in with the prefix, most of the existing Blazor libraries went with this route so this is a good call

[wdcossey]

IMHO Bb is a better prefix and I think it fits well with the name of the project.

Could also use a 3 char prefix [that's even less likely to have a collision], something like Blu

• BluButton
• BluCombobox
• BluDialog

PS: Don't be worried about major version releases, also don't need to focus on backwards compatibility [in the early stages], all is needed is a set of release notes, state the breaking changes and how to move forward.

You could also just release versions based on the {year}.{month}.{build} [and not worry going forward]

• 26.01.0123
• 26.02.1543

[mathewtaylor]

Yea, I went with Bb in the end :)

[jimmyps]

Congrats on the new release, glad to see some of my contributions are included into v3 :)

[mathewtaylor]

Some nice ideas for performance enhancements - good work on those.

[jimmyps]

Yep, has been authoring UI components for decades back in the WebUI/Silverlight era.. then founded a SaaS commerce platform and recently exited, and now looks like great time to be back again to building components with modern approaches.

Btw would appreciate for cross attribution as well :) Got bunch of new stuff in my upcoming roadmap, will share more later on.

[mathewtaylor]

Blazor Blueprint v3 has been released. There are a lot of changes in this release and as mentioned these are breaking changes. You can see the migration guide here https://github.com/blazorblueprintui/ui/blob/main/V3-MIGRATION-GUIDE.md and the changelog here https://github.com/blazorblueprintui/ui/blob/main/CHANGELOG.md.

There are a couple of open PRs on v2, I will see how to bring them into the v3 branch instead.

As usual, feedback is always welcome 👍🏻 and I hope you enjoy these updates.