The main part of the docs that are interesting/relevant to people who are using the CT is those that represent the integrations and how they can use them.
To ensure that the docs are easily discoverable, the integration docs will live in the dotnet/docs-aspire repo, in a new section that is to be created. This means they will be formatted in the format of other .NET Aspire integration docs. While the creator/owner of an integration will be expected to maintain the doc in the dotnet/docs-aspire repo (update it with API changes, etc.), I (@aaronpowell) will be the one to sign off on the review and ensure it gets merged, with @IEvangelist as the fallback if I'm unavailable.
This repo will still contain some minimal documentation that is more specific around the contributing side of the project, governance, etc. These files will live in the docs folder.
PR #53 has undertaken the initial work to remove the old integration docs, expanded the contributor guide and refactored the NuGet package README workflow.
The main part of the docs that are interesting/relevant to people who are using the CT is those that represent the integrations and how they can use them.
To ensure that the docs are easily discoverable, the integration docs will live in the
dotnet/docs-aspirerepo, in a new section that is to be created. This means they will be formatted in the format of other .NET Aspire integration docs. While the creator/owner of an integration will be expected to maintain the doc in thedotnet/docs-aspirerepo (update it with API changes, etc.), I (@aaronpowell) will be the one to sign off on the review and ensure it gets merged, with @IEvangelist as the fallback if I'm unavailable.This repo will still contain some minimal documentation that is more specific around the contributing side of the project, governance, etc. These files will live in the
docsfolder.PR #53 has undertaken the initial work to remove the old integration docs, expanded the contributor guide and refactored the NuGet package README workflow.