API Documentation

[Redth]

We currently have some API doc support happening for Inline XML code docs (there is a separate issue for reviewing and documenting requirements around inline docs: #3936 )

We also have an existing set of API Docs for Xamarin.Forms: https://github.com/xamarin/Xamarin.Forms-api-docs

We need to decide on the best way forward to complete the MAUI API docs. There's some questions around the best way to do this. Here's a few questions to provoke some thoughts:

• Do we write some automation to bring the existing Forms API docs over and rework namespaces?

• If we port existing docs, should we mostly add tags inline in code to point to the old docs?

• There's some longer docs that would be messy to inline in source code, should these be split into conceptual docs and shortened/linked to conceptual docs in the API docs?

• First pass at porting doc comments from Forms API docs #4099 - Imported old api docs via inline xml doc comment imports

• API docs need to be available on the API browser Available on https://learn.microsoft.com/en-us/dotnet/api/?view=net-maui-6.0

• What is the status of the .NET MAUI Docs? #8689

• Add missing MAUI API docs #7463

[hartez]

#4099

[hartez]

Linking issues here so we can update/close when this is done: #8689 #7463

[mattleibow]

Closing this as many APIs are now documented using inline docs. Any missing ones can be implemented as they appear and do not require a mega issue to track it.