Skip to content

Consider splitting the Blazor *Routing and Navigation* fundamentals article #35683

@guardrex

Description

@guardrex

Description

This could become a node of a few articles, or perhaps it would be best to continue to have one article here covering only the fundamental routing and navigation concepts with the rest going into a new Routing and Navigation advanced concepts article later in the ToC.

How about we split the routing and navigation article into two separate articles: one on routing and one on navigation? I think the routing content could also uses some restructuring. It doesn’t really start off explaining what routing is all about. The first section is about static vs interactive routing, which is fine content, but the user doesn’t know what routing is yet at this point. Routing is how requests or page navigations get handled by specific components. You specify routes for your components using @page. Routing is handled by the Router component and the ASP.NET Core endpoint routing system. Etc.

For basic definitions, we're still assuming that the Blazor doc set is an extension of the main doc set. However, we don't say so at the top of the article, so that's not ideal. Specifically for Blazor routing, this section in the Components overview would be better in at the top of the Routing article ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/?view=aspnetcore-9.0#routing

... and then we can look at how to split it and improve the content and organization.

That makes sense. I still think though that there are some Blazor specific routing concepts that are worth mentioning at the beginning of the article to introduce the topic. Stuff like: “Blazor uses routing to direct requests and page navigations to specific components. To apply a route to a component use the @page directive.” Etc. I agree that moving the Routing section you referenced to the top of the doc would go a long way to addressing this. I’m just trying to make sure that all our docs start with the basic concepts and then progress naturally from there.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/routing?view=aspnetcore-9.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/fundamentals/routing.md

Document ID

b6cb2574-6326-a40d-0b6c-d1661328e828

Platform Id

4dcb037e-b606-e05a-a733-1458d2ce3914

Article author

@guardrex

Metadata

  • ID: 35474d24-8039-f04a-de14-1530b8e8506c
  • PlatformId: 4dcb037e-b606-e05a-a733-1458d2ce3914
  • Service: aspnet-core
  • Sub-service: blazor

Related Issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions