New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Focus on improving content health score #32305
Labels
Comments
Tutorial: Call an ASP.NET Core web API with JavaScript
|
This was referenced Apr 24, 2024
wadepickett
added
reQUEST
Triggers an issue to be imported into Quest
and removed
reQUEST
Triggers an issue to be imported into Quest
labels
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dedicate some time to have an impact on improving factors related to the content health score (see the reporting):
1: Improve freshness where I can have the most impact. High traffic, >365 days for example.
2. Nagging doc build validation issues and have the most impact on the freshness where I can.
If I have some time as a priority 2, hit on the asp.net framework repo a bit too.
Per doc manager this is only to be hit after all other current April commitments accomplished, so any extra time left over, I don't hit more from the high priority in backlog, but instead make some progress on this for the repo.
Associated Internal tracking: DevOps 250767
The text was updated successfully, but these errors were encountered: