I forgot which repo the docs belong to, sorry.

@guardrex What is the "WN article" you are referring to?

What's New article

Will we write an article to cover the Blazor WebAssembly-specific counters that would dovetail with our main doc set guidance on Performance Diagnostics? If so, then it seems that we'll move our current Blazor node Performance article content into an overview article of a new Blazor node Performance node (folder) and add a new article here. If not, then I assume that you just want an entry in the WN article covering this.

I think we need an article covering the new performance profiling and memory diagnostic tooling. Putting that content under a new Blazor Performance node sounds great. I think it would help to also reference this content from the related articles in the ASP.NET Core Performance section, like from the Performance Diagnostic Tools and Memory and GC articles.

Very well ... I'll see about getting this drafted on a PR soon.

@guardrex let's only document the use-cases triggered via JS which triggerst the download of .nettrace file from the browser.
The ds-router experience mostly works, but it's quite more complex to setup. So I would not lead users toward it for now.

I'm just about done with the draft PR. Let's strike whatever you want from the PR when it goes up.