Skip to content

*Render Modes* article improvements #35718

@guardrex

Description

@guardrex

Description

I kind'a think it's ok at its current length, but we've had one dev say that they think it's too long.

Should it be split into a node (folder) of ~3 articles?

I think I prefer keeping the render modes article as one article, but maybe we could simplify the article a bit? Are there ways we could make it less verbose? The last few sections seem a little bit random:

  • Discover components from additional assemblies - Why is this here? It’s covered in the routing & navigation article. Delete?
  • Closure of circuits when there are no remaining Interactive Server components - Shouldn’t this just be a note in the interactive server-side rendering section?
  • Custom shorthand render modes - This section is pretty long to show folks some C# tricks to simplify setting up a custom render mode. Could we just add a short note about this approach in the Apply a render mode programmatically section?
  • Service injection via a top-level imports file (_Imports.razor) - This section doesn’t seem related to render modes. Honestly, I don’t really understand what problem it’s trying to address. Delete?

Page URL

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

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/render-modes.md

Document ID

7c9948a3-9886-8097-6014-492a4c21ea4e

Platform Id

d841acf1-aef5-10fc-d53a-e22f0dc84234

Article author

@guardrex

Metadata

  • ID: 7c9948a3-9886-8097-6014-492a4c21ea4e
  • PlatformId: d841acf1-aef5-10fc-d53a-e22f0dc84234
  • Service: aspnet-core
  • Sub-service: blazor

Related Issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions