Skip to content

Consolidate and unify the Blazor Web App and Blazor WebAssembly App content on the Blazor overview page #30285

@danroth27

Description

@danroth27

Note: I'm opening this tracking issue now to revisit the Blazor overview doc, but this can wait until after RC1.

In .NET 8 we're working to make Blazor a single solution for frontend web development. Blazor can now handle all of your web UI needs. If you're building a web app with .NET 8 you just use Blazor.

The .NET 8 version of the Blazor overview doc pivots pretty heavily on the Blazor templates (Blazor Web App, Blazor WebAssembly, Blazor Hybrid). This is understandable given that the previous version of the doc pivoted heavily on the Blazor hosting models, which mapped directly to templates. But in .NET 8 we want to present a more unified message: you just use Blazor to build your web app, and Blazor provides different capabilities to accommodate your needs.

To present a more unified story I think we should consolidate the Blazor Web App and Blazor WebAssembly sections and instead focus more on the job to be done, which is to build a web app or a native client app. I think in general we want the overview doc to focus more on what Blazor is and why should you use it, and less on how you use it. This doc could probably be a lot shorter and with fewer details that get covered in other docs. Let's figure this out post RC1.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

  • ID: 5bc28995-6784-a7d2-5c0b-9811a8d19c1a
  • Version Independent ID: 1668c8fb-024c-c86d-d4d5-e22e3355c04b
  • Content: ASP.NET Core Blazor
  • Content Source: aspnetcore/blazor/index.md
  • Product: aspnet-core
  • Technology: aspnetcore-blazor
  • GitHub Login: @guardrex
  • Microsoft Alias: riande

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions