ASP.NET Core namespaces don't have summary descriptions. Compare:
ASP.NET Core API Reference vs .NET API Reference.
Namespaces don't have /// comments, and so are documented in dotnet/AspNetApiDocs XML files. Namespace XML files aren't overwritten by doc sync.
Information about how to write a namespace summary: https://github.com/dotnet/dotnet-api-docs/wiki/Summary:-Namespace
There are 159 namespaces to do, so lots of work for everyone. I've tried to give people namespaces that they worked on or are familiar with. Search for your GitHub name in the browser to highlight your namespaces.
Example PR for adding namespace summary: https://github.com/dotnet/AspNetApiDocs/pull/168
Scale how detailed the summary is based on the namespace. One sentence is fine for most. More popular or complex namespaces can be up to a paragraph. Also, remarks can be used to link to relevent conceptual articles.
Note: remove /en-us/ and version number from conceptual article URLs. That allows the site to redirect the browser to the best language/version for them.
@JamesNK the examples you sited are for the 5.0 docs. Which branch should we target in our docs PRs to get the changes into those views❔
Target master for now. I'll enquire about how versioning works in that repo.
Most helpful comment
Example PR for adding namespace summary: https://github.com/dotnet/AspNetApiDocs/pull/168
Scale how detailed the summary is based on the namespace. One sentence is fine for most. More popular or complex namespaces can be up to a paragraph. Also, remarks can be used to link to relevent conceptual articles.
Note: remove
/en-us/and version number from conceptual article URLs. That allows the site to redirect the browser to the best language/version for them.