Components, done "right" carry tremendous potential to speed up your web development, but get it wrong and you'll miss out on all the potential benefits

When you navigate to the same component in Blazor it will bypass some of the component lifecycle events

How to handle Component A needs to talk to Component B challenges in Blazor

Sure you could just keep throwing StateHasChanged calls at your component until it finally re-renders, but what's really going on behind the scenes?

Data coming from another service/API needs to be mapped into a different type for your Blazor component, so where should you perform the mapping?

Blazor's component model can make you a lot more productive, if you let it…

Blazor Server and WASM both have trade-offs, Blazor United looks set to tackle those and make Blazor a viable framework for all your web development needs.

How to render nested "nodes" in a TreeView

Maintain clear separation between your components and "inject" the markup you need

Render Blazor components from dynamic content, at runtime?

Prioritise the ability to iterate and evolve your UI

Build the skeleton and fill in the details from there

Make your Blazor app support deep linking by passing state in the Query String

Sometimes you'll want your Blazor UI to change according to the data you're using to populate it

Big feels overwhelming so start small and go from there.

Struggling to get "in" to a feature, or know where to start? Try sketching out a mockup.

Tailwind 3 automatically scans your site for html files, Blazor components, other templates in order to generate a static CSS file for your site, but it's a faff to launch Tailwind and your Blazor app separately...

The new Razor editor in Visual Studio 2022 doesn't currently provide intellisense for stylesheets you reference from external sources like NuGet packages…

Don't rush to break your UI down into separate components (too soon)

Consistency is key and make your components work harder to prove they're actually the 'same thing'