[Tracking Issue] New Components topic sections about blazor.docs HOT 8 CLOSED

I'd like to move NavLink and the routing content from the current Components article into the new Routing topic.

from blazor.docs.

@SteveSandersonMS

The top level topics that make sense to me from this list are:

• ...
• Components (these could be subtopics or sections in a single article)
  • Component classes
  • Using components
  • Component parameters
  • Child content
  • Data binding
  • Event handling
  • Lifecycle methods
  • Disposal
  • Using a code-behind file (@inherits today, partials in the future) #73
  • Razor support
• Building component libraries #70
• Routing (covers @page and NavLinks) #72
• Logging (not currently a feature)
• Error handling? (not sure what this would cover . . .)
• JavaScript interop #59
• ...

from blazor.docs.

Closing as all the proposed changes are tracked by separate issues

from blazor.docs.

I was thinking along the lines that this is a tracking issue for only the Components topic ... that these would end up being sections and that we'd track the work here.

from blazor.docs.

I'll move this information WRT new sections for the Components topic that isn't an issue yet over to the high-level planning outline ... just so that we have an easy spot to keep it for reference.

from blazor.docs.

@danroth27 I updated the high-level planning outline with the work done and your notes above.

btw - We originally had "NavLink" in a section of the Components topic called "Built-in Blazor components."

https://github.com/aspnet/Blazor.Docs/wiki/Blazor-high-level-planning

from blazor.docs.

We originally had "NavLink" in a section of the Components topic called "Built-in Blazor components."

Yeah, but I don't think we have enough built-in components to have separate topic.

from blazor.docs.

I meant do you want it in the upcoming Routing topic or left in the Components topic?

from blazor.docs.