Hi folks,
Great news! Last Friday, we moved ~17k WDK reference (API/DDI) documentation pages from MSDN to the Docs platform. This means that you can now click Edit and submit pull requests against the reference content, just as you have been able to do for the last two years with the conceptual docs.
But the really cool part is that the new ref rig is backed by an API catalog. Every day, the catalog diffs the latest Windows header files, and then builds doc stubs that match the headers. The descriptions and remarks are then injected in. So we guarantee fidelity against headers, and we gain all the advantages of using a Git/Markdown-based authoring system.
The WDK doc root is https://docs.microsoft.com/en-us/windows-hardware/drivers/. Click the DDI Reference tile to go into the new ref, which is organized by header.
Note that search engines are still catching up. IOW, if you search for your favorite API today, the result will likely say MSDN, but when you click it, you’ll get auto redirected to the Markdown-based page on Docs.microsoft.com.
We’ve been working on this one for a long time, and we hope you’ll be as delighted with the result as we are. 
Ted Hudek
Senior Content Developer
Windows IHV and Devices Development
Today, I am a happy man.
On Mon, Jan 22, 2018 at 7:11 PM, xxxxx@microsoft.com
wrote:
> Hi folks,
>
> Great news! Last Friday, we moved ~17k WDK reference (API/DDI) documentation pages from MSDN to the Docs platform. This means that you can now click Edit and submit pull requests against the reference content, just as you have been able to do for the last two years with the conceptual docs.
>
> But the really cool part is that the new ref rig is backed by an API catalog. Every day, the catalog diffs the latest Windows header files, and then builds doc stubs that match the headers. The descriptions and remarks are then injected in. So we guarantee fidelity against headers, and we gain all the advantages of using a Git/Markdown-based authoring system.
>
> The WDK doc root is https://docs.microsoft.com/en-us/windows-hardware/drivers/. Click the DDI Reference tile to go into the new ref, which is organized by header.
>
> Note that search engines are still catching up. IOW, if you search for your favorite API today, the result will likely say MSDN, but when you click it, you’ll get auto redirected to the Markdown-based page on Docs.microsoft.com.
>
> We’ve been working on this one for a long time, and we hope you’ll be as delighted with the result as we are.
>
> Ted Hudek
> Senior Content Developer
> Windows IHV and Devices Development
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>
Awesome stuff!
Gabriel Bercea
www.kasardia.com
On Tue, Jan 23, 2018 at 2:33 AM, xxxxx@gmail.com
wrote:
> Today, I am a happy man.
>
> On Mon, Jan 22, 2018 at 7:11 PM, xxxxx@microsoft.com
> wrote:
> > Hi folks,
> >
> > Great news! Last Friday, we moved ~17k WDK reference (API/DDI)
> documentation pages from MSDN to the Docs platform. This means that you
> can now click Edit and submit pull requests against the reference content,
> just as you have been able to do for the last two years with the conceptual
> docs.
> >
> > But the really cool part is that the new ref rig is backed by an API
> catalog. Every day, the catalog diffs the latest Windows header files, and
> then builds doc stubs that match the headers. The descriptions and remarks
> are then injected in. So we guarantee fidelity against headers, and we
> gain all the advantages of using a Git/Markdown-based authoring system.
> >
> > The WDK doc root is https://docs.microsoft.com/en-
> us/windows-hardware/drivers/. Click the DDI Reference tile to go into
> the new ref, which is organized by header.
> >
> > Note that search engines are still catching up. IOW, if you search for
> your favorite API today, the result will likely say MSDN, but when you
> click it, you’ll get auto redirected to the Markdown-based page on
> Docs.microsoft.com.
> >
> > We’ve been working on this one for a long time, and we hope you’ll be as
> delighted with the result as we are.
> >
> > Ted Hudek
> > Senior Content Developer
> > Windows IHV and Devices Development
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > Visit the list online at: http:> showlists.cfm?list=ntdev>
> >
> > MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> > Details at http:
> >
> > To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
–
Bercea. G.</http:></http:></http:></http:>
That IS very cool. Nice work!
And the ability to send a PR for doc changes can only be viewed as added value for the community.
Thanks, Ted, for keeping us all informed.
Peter
OSR
@OSRDrivers