Docs (.NET 10): Prepare focused PR(s) for .NET MAUI .NET 10 updates — information required

Purpose

Create focused PRs to update .NET MAUI docs for .NET 10 following the team's lightweight process and guardrails. This draft tracks the scope, files, verification links, and PR checklist so we can open small topic-focused PR(s) directly to main.

Scope (initial)

- Target repo: dotnet/docs-maui
- Target branch(es): small, topic-focused branches off main (e.g., pr01-pop-ups-async-from-main)
- Topics to consider: Pop-ups, Media picker multi-select, Gestures deprecations, other .NET 10 API changes

Verification & links

- Link upstream MAUI PR(s)/commits used to verify behavior: (provide URLs)
- Files to change: (list specific doc pages or includes; e.g., includes/pop-ups-dotnet10.md)

Checklist

- Use moniker blocks for <= .NET 9 and >= .NET 10 where appropriate
- Keep PRs small and focused; update ms.date on materially changed pages
- Verify xrefs, build moniker warnings, and API names
- Include platform notes and samples where needed

Information needed from the author to complete this issue

1. Which exact doc pages or include files should be updated? Please provide file paths or page URLs.
2. For each topic, link to the upstream MAUI PR(s) or commit(s) that introduced the .NET 10 change.
3. Which sample code or snippets should be updated or added? (If yes, provide file paths or a brief code example.)
4. Do you want these changes grouped into a single PR or multiple small PRs per topic? If multiple, list desired PR branch names.
5. Any platform-specific notes to call out (Android/iOS/Mac Catalyst/Windows)?
6. Desired labels, milestone, or project to apply to the PR(s).
7. Who should be requested as reviewers beyond CODEOWNERS?

Notes

- If you prefer, answer in one message listing items 1–7; I will update this draft accordingly and expand the checklist and files changed. If you provide upstream MAUI links and file paths, I can also include Code snippets and verification notes in the draft.
### [](url)

Start by identifying the exact doc pages or includes, including any relevant files such as includes/pop-ups-dotnet10.md, and link the upstream MAUI PRs or commits. Record required samples, platform notes, PR grouping, and verification details. Done means the scope, source links, files, and checklist are specific enough to prepare focused PRs.

Written by the indexing model from the issue text.