Docfx: [Question] Current status for the new version 3.0.
This is just a question, because unfortunately the project for version 3.0 was removed, and also the milestone. The linked roadmap for version 3.0 is not up to date anymore. And so I just wanted to ask about the current state of things. Until when is version 3.0 planned? How many features are still missing? When should you upgrade documentation from the current version 2.0 to version 3.0? Are there any best practices? Pre-releases can already be installed. Do they make sense?
I would like some short answers here. Then we can close this issue very quickly!
Many thanks for the help in advance!
FSharpCSharp
All 4 comments
Thank you for bringing up this concern.
We've recently moved work item tracking from GitHub to azure devops for v3 because it gives us better tracking across features within Microsoft. The projects and issues for v3 are gradually removed from GitHub, but we are still actively developing it on GitHub.
We've made good progress on v3 for https://docs.microsoft.com (our first party consumer). Several repos under MicrosoftDocs have been using v3 in production, and we are kicking off massive v3 migration for the rest.
On the community side, v3 still misses two critical parts: template and .NET api document extractor. The pre-release is production quality for _docs.microsoft.com_, but it might not make sense for the community at the moment due to lacking of template and .NET api doc.
yufeih
on 15 Jul 2019
Thank you for your feedback! It's good to hear that things are definitely moving on. It was also on the old agenda (please correct me if I am wrong) that the automatic PDF generation and linking should be available by default in the template and during creation. An important point that was still on the old roadmap was localization.
Does it go on in these points, or have they been postponed? To my knowledge at least the PDF functionality was already part of docs.microsoft.com.
FSharpCSharp
on 15 Jul 2019
I've updated roadmap to reflect a more recent status.
yufeih
on 15 Jul 2019
Thank you very much. With that we can close this issue. All questions answered! Super, thank you very much for the quick and detailed reaction.
FSharpCSharp
on 16 Jul 2019
Related issues
Rora
路
4Comments
eberjoe
路
3Comments
vicancy
路
4Comments
mrEDitor
路
3Comments
guardrex
路
5Comments
Most helpful comment
Thank you for bringing up this concern.
We've recently moved work item tracking from GitHub to azure devops for v3 because it gives us better tracking across features within Microsoft. The projects and issues for v3 are gradually removed from GitHub, but we are still actively developing it on GitHub.
We've made good progress on v3 for https://docs.microsoft.com (our first party consumer). Several repos under MicrosoftDocs have been using v3 in production, and we are kicking off massive v3 migration for the rest.
On the community side, v3 still misses two critical parts: template and .NET api document extractor. The pre-release is production quality for _docs.microsoft.com_, but it might not make sense for the community at the moment due to lacking of template and .NET api doc.