Blazor forms node

[guardrex]

Fixes #30618

The ToC for this restructuring the single article into this node of articles is at #30618 (comment).

Notes

• Starts with the plain HTML forms section, then rolls into EditForm-based forms. It switches over quickly after just one example. How many forms features do you want plain forms to cover with examples and text before switching over to EditForm?
• We need to confirm the plain HTML form remarks. I'm assuming that enhanced nav and streaming rendering are good.
• ❓on how Blazor knows to bind the model to a plain form without something like "@model" (or similar). I'd like to have the section explain why it isn't necessary.
• Currently, the What's New article merely points to the Overview, but I plan to enhance What's New coverage and point directly at the new 8.0 feature sections across this node. That will be on a separate PR later.

---

Internal previews

Toggle expand/collapse

📄 File	🔗 Preview link
aspnetcore/blazor/components/built-in-components.md	ASP.NET Core built-in Razor components
aspnetcore/blazor/components/data-binding.md	ASP.NET Core Blazor data binding
aspnetcore/blazor/components/integration.md	Integrate ASP.NET Core Razor components into ASP.NET Core apps
aspnetcore/blazor/components/lifecycle.md	aspnetcore/blazor/components/lifecycle
aspnetcore/blazor/file-downloads.md	ASP.NET Core Blazor file downloads
aspnetcore/blazor/file-uploads.md	ASP.NET Core Blazor file uploads
aspnetcore/blazor/forms/binding.md	aspnetcore/blazor/forms/binding
aspnetcore/blazor/forms/index.md	aspnetcore/blazor/forms/index
aspnetcore/blazor/forms/input-components.md	aspnetcore/blazor/forms/input-components
aspnetcore/blazor/forms/troubleshoot.md	aspnetcore/blazor/forms/troubleshoot
aspnetcore/blazor/forms/validation.md	aspnetcore/blazor/forms/validation
aspnetcore/blazor/fundamentals/signalr.md	ASP.NET Core Blazor SignalR guidance
aspnetcore/blazor/javascript-interoperability/call-dotnet-from-javascript.md	Call .NET methods from JavaScript functions in ASP.NET Core Blazor
aspnetcore/blazor/security/index.md	aspnetcore/blazor/security/index
aspnetcore/blazor/security/server/additional-scenarios.md	Server-side ASP.NET Core Blazor additional security scenarios
aspnetcore/blazor/security/server/threat-mitigation.md	Threat mitigation guidance for server-side ASP.NET Core Blazor
aspnetcore/blazor/webassembly-lazy-load-assemblies.md	Lazy load assemblies in ASP.NET Core Blazor WebAssembly
aspnetcore/release-notes/aspnetcore-5.0.md	aspnetcore/release-notes/aspnetcore-5.0
aspnetcore/release-notes/aspnetcore-6.0.md	What's new in ASP.NET Core 6.0
aspnetcore/release-notes/aspnetcore-7.0.md	What's new in ASP.NET Core 7.0
aspnetcore/release-notes/aspnetcore-8.0.md	What's new in ASP.NET Core 8.0
aspnetcore/whats-new/dotnet-AspNetCore.Docs-mod0.md	aspnetcore/whats-new/dotnet-AspNetCore.Docs-mod0
aspnetcore/whats-new/dotnet-AspNetCore.Docs-mod2.md	ASP.NET Core docs: What's new for August 2023
aspnetcore/whats-new/dotnet-AspNetCore.Docs-mod3.md	"ASP.NET Core docs: What's new for September 2023"

[guardrex]

@Rick-Anderson ... There's a build system failure here.

The build report indicates a problem with a stale UID ...

https://buildapi.docs.microsoft.com/Output/PullRequest/332f35cd-658d-4914-0f85-907e40ee89f0/202311011336064978-30834/BuildReport?accessString=6dc5e6006018399fe4db34432638b0f75e004a3ef0a256f1bd04038b1925fc95

... but that file at ...

https://github.com/dotnet/AspNetCore.Docs/blob/guardrex/blazor-forms/aspnetcore/whats-new/dotnet-AspNetCore.Docs-mod4.md

... has no such reference.

Also, I think it is time that I get some super powers here 💪. This is the second time in a few weeks that we've hit silly build problems that hold up work. I only get the auto-merge option on even a warning. I'd like to be able to override the build warning status in situations like this to merge and move on 🏃‍♂️. I'm too busy to get held up like this.

[Rick-Anderson]

@guardrex let me know when to S&M and cc @tdykstra so he can beat me to it.

[guardrex]

@Rick-Anderson ... You can go ahead and S&M. The build warning doesn't seem to be correct looking at that file, so I'm not sure what's going on there.