Make sure .NET WebAssembly runtime features are properly documented

[danroth27]

We have a bunch of great content in https://github.com/dotnet/runtime/blob/main/src/mono/wasm/features.md about various features of the .NET WebAssembly runtime. We should make sure the relevant user facing features from this doc are covered in our official docs on Microsoft Learn, so they are discoverable, appropriately localized, etc.

This issue tracks going through the features.md doc and creating issues in the dotnet/aspnetcore.docs for any official doc content that should be added.

@guardrex

[guardrex]

Let me know if you'd like me to create a "Runtime" node of articles in the ASP.NET Core Blazor doc set, holding articles created from the features.md article or pointing to existing Learn-hosted content. A single issue over there could be set up to resolve it.

[pavelsavara]

@danroth27

• some of the features in that article are mono specific (like MONO_LOG_MASK)
• Some of them are not really supported, Like any native C library integrations or any EMCC compiler flags. They are strongly in "use only if you know what you are doing".
• some of them change in time, like MSBuild properties. Do we want to make them public/backward compatible ?
• there is opinionated advice in that article, about web development in general, that may help our audience. But I'm not sure how authoritative tone we want to use in oficiall docs.

Which of that do you want to make official ?

@guardrex What page structure do you imagine for it ?

[guardrex]

Some of it is already covered in various places in the Blazor node.

It looks like for what's left (and with a few cuts for things that you don't want in a Learn article) that the length of features.md is fine for one new article added to the Blazor node.

A new article with what isn't already covered (and sans anything you don't want) could go early in the Blazor node if you want things covered as preliminary concepts, or a new article could go near the bottom of the Blazor node ToC because this would be advanced or less required content in most development.

Please open a doc issue when ready to get the process started, indicating ...

• Which sections I should ignore when drafting the content.
• Any coverage notes and gotchas 😈 for the sections.
• Where you want the new article in the Blazor node ToC.

[pavelsavara]

I don't want to commit any of the behaviors as public/supported/documented. We documented most of the public ones in the past.