@MackinnonBuck ... This pertains to your work and the doc coverage for Blazor <head> modification using a section-based approach (dotnet/aspnetcore #34218).
I'm updating our list of built-in components at ...
https://docs.microsoft.com/aspnet/core/blazor/components/built-in-components
I checked for anything implementing IComponent that may have been missed and found a sneaky one that got away from me ... RouteView 😈 ... I'll get that sucker in there! UPDATE: Lick'd IT! 🐄👅 on #26100.
I noticed two more that we didn't discuss when adding the guidance for controlling <head> content:
I only see them used in framework code via OpenComponent. Are those two primarily (or only) for internal framework use to get HeadOutlet, HeadContent, and PageTitle components working, or can those be used directly by devs in other scenarios? If they could be used by devs, can you scope the scenarios for their use and perhaps provide (or just describe) a quick example (or a few examples)?
Depending if we proceed and what you suggest for dev use cases, any of the following are possible for location ...
-
Find a more general spot for the coverage if it's more general than just controlling <head> content, perhaps in the Components overview topic at the bottom of the coverage.
-
Place the guidance in this topic and either ...
a. Broaden this topic from Control <head> content to Control <head> content and XXXXXXXX ... depending on how you would describe their use. Place a new section at the bottom of this topic.
b. Don't broaden the topic. Leave the title alone. Place a new section at the bottom of this topic, and angle the guidance along the lines of 'the framework uses these components for HeadOutlet, HeadContent, and PageTitle functioning but they can be used in other use cases, such as ... XXXXXXXX.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@MackinnonBuck ... This pertains to your work and the doc coverage for Blazor <head> modification using a section-based approach (dotnet/aspnetcore #34218).
I'm updating our list of built-in components at ...
https://docs.microsoft.com/aspnet/core/blazor/components/built-in-components
I checked for anything implementing
IComponentthat may have been missed and found a sneaky one that got away from me ...RouteView😈 ... I'll get that sucker in there! UPDATE: Lick'd IT! 🐄👅 on #26100.I noticed two more that we didn't discuss when adding the guidance for controlling
<head>content:I only see them used in framework code via
OpenComponent. Are those two primarily (or only) for internal framework use to getHeadOutlet,HeadContent, andPageTitlecomponents working, or can those be used directly by devs in other scenarios? If they could be used by devs, can you scope the scenarios for their use and perhaps provide (or just describe) a quick example (or a few examples)?Depending if we proceed and what you suggest for dev use cases, any of the following are possible for location ...
Find a more general spot for the coverage if it's more general than just controlling <head> content, perhaps in the Components overview topic at the bottom of the coverage.
Place the guidance in this topic and either ...
a. Broaden this topic from Control <head> content to Control <head> content and XXXXXXXX ... depending on how you would describe their use. Place a new section at the bottom of this topic.
b. Don't broaden the topic. Leave the title alone. Place a new section at the bottom of this topic, and angle the guidance along the lines of 'the framework uses these components for
HeadOutlet,HeadContent, andPageTitlefunctioning but they can be used in other use cases, such as ... XXXXXXXX.Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.