What part of the documentation needs improvement?
Microsoft Learn content for modern Windows app development still links extensively to UWP projects in microsoft/Windows-universal-samples. The MicrosoftDocs/windows-dev-docs repository alone currently contains roughly 193 files with such references, including pages under current /windows/apps/develop/ guidance.
As migrated WinUI 3 samples land in microsoft/WindowsAppSDK-Samples, applicable pages should link to those maintained projects instead. This must be an audited mapping rather than a global replacement because UWP-specific reference content may correctly retain its original sample links.
Describe the change you'd like
Create an inventory of documentation references to Windows-universal-samples and update each applicable page to point to the corresponding migrated WinUI 3 sample after that sample lands on the destination repository's main branch.
The work should:
- Map each legacy sample and scenario to its new
WindowsAppSDK-Samples location.
- Prioritize current Windows app development and Windows App SDK documentation.
- Update sample links, surrounding framework terminology, prerequisites, build instructions, and code-path references where necessary.
- Verify that every replacement target exists on
main and links to the correct scenario rather than only the repository root.
- Record intentional UWP-only references with a reason instead of changing them blindly.
- Coordinate additional documentation repositories, including generated WinRT API documentation, as a separately reviewed phase where ownership or generation differs.
- Track documentation pull requests back to the corresponding sample landing pull requests.
Completion criteria
- All in-scope modern Windows documentation references have been reviewed.
- Applicable links point to buildable WinUI 3 samples on
WindowsAppSDK-Samples/main.
- Intentional legacy references are documented.
- Updated links and surrounding instructions pass the owning documentation repositories' validation checks.
Additional context
This issue depends on the sample-porting and destination-structure work. Documentation updates should follow sample merges so public links never target unmerged branches. The initial count is a sizing estimate and should be replaced by a checked-in or attached audit inventory before bulk updates begin.
What part of the documentation needs improvement?
Microsoft Learn content for modern Windows app development still links extensively to UWP projects in
microsoft/Windows-universal-samples. TheMicrosoftDocs/windows-dev-docsrepository alone currently contains roughly 193 files with such references, including pages under current/windows/apps/develop/guidance.As migrated WinUI 3 samples land in
microsoft/WindowsAppSDK-Samples, applicable pages should link to those maintained projects instead. This must be an audited mapping rather than a global replacement because UWP-specific reference content may correctly retain its original sample links.Describe the change you'd like
Create an inventory of documentation references to
Windows-universal-samplesand update each applicable page to point to the corresponding migrated WinUI 3 sample after that sample lands on the destination repository'smainbranch.The work should:
WindowsAppSDK-Sampleslocation.mainand links to the correct scenario rather than only the repository root.Completion criteria
WindowsAppSDK-Samples/main.Additional context
This issue depends on the sample-porting and destination-structure work. Documentation updates should follow sample merges so public links never target unmerged branches. The initial count is a sizing estimate and should be replaced by a checked-in or attached audit inventory before bulk updates begin.