docs: Unofficial name "Blazor component" in use

[guardrex]

🙋 Documentation Request

"Blazor component" is an unofficial name. The official name of a component in Blazor is "Razor component." See the third paragraph of ...

https://learn.microsoft.com/aspnet/core/blazor/fundamentals/#razor-components

... and the first paragraph of ...

https://learn.microsoft.com/aspnet/core/blazor/components/#razor-components

"Blazor component" isn't used by the Blazor doc set.

💁 Possible Solution

To better align the FluentUI doc set with the Blazor doc set, I recommend performing a find-'n-replace on all instances of "Blazor component," replacing it with "Razor component."

I volunteer to submit a PR to address this if the maintainers approve my recommendation.

[vnbaaij]

@guardrex as the master of docs..., how to best change

The Fluent UI Blazor library provides a robust and extensive set of Blazor components.

Something like:

The Fluent UI Blazor library provides a robust and extensive set of Razor components for Blazor applications.

Suggestions appreciated!

[guardrex]

Yes, that's right.

The reason that I closed this is that it has been such a losing battle for me. I've discussed my concern about the naming with Dan Roth over the years, and it's unfortunate that there are two names for the same thing. The official name was always been "Razor component;" but many developers, even at MS, are using "Blazor component." Even Dan uses "Blazor component" in presentations and casual conversation. When I see it, it still bothers me a little bit ... I feel like I have a touch of OCD when I see it. 😆

I think you can probably just leave it as "Blazor component." Just note that "Blazor component" isn't the official name and doesn't match the Blazor docs. It's possible one day that someone will open an issue here confused about "Razor component" versus "Blazor component," but issues don't ever seem to come in on the subject ... at least on the ASP.NET Core docs repo.

[MarvinKlein1508]

@guardrex a wise man once said when everybody is doing it wrong, the process will shift and make the wrong one right.

I think somewhere in the future everybody will call it Blazor component. You won't believe how many new people to the framework are confused that they need to add a razor component when they work with Blazor. At least in my dev career I've witnessed 5 developers about this topic.

[guardrex]

I tried multiple times to stop this from happening, but ... well ... it happened. 🙈😢😆 Having two names for the same thing with both in wide use is an unfortunate outcome. In the experimental days even before Blazor became an official MS product, I raised this subject with Dan a couple of times. At one point, he considered having all of the Blazor docs adopt "Blazor component;" but ultimately, he decided not to make the change. I don't recall the exact reason. Anyway, I'm trying to overcome my OCD 😄 about it. He's aware of the situation. I'm sure he'll let me know if he decides to adopt "Blazor component" as the official name.

[vnbaaij]

For my fellow OCD'er @guardrex ... #3705

[guardrex]

Thanks @vnbaaij! 🎷

I won't need to see a therapist ... well ... today anyway! 🤣

[MarvinKlein1508]

@guardrex don't worry. I got you:

[vnbaaij]

@MarvinKlein1508 don't they always say music is good therapy 🪗?

[MarvinKlein1508]

@vnbaaij of course. I can't code without some good music.