Restructure TOC by audience (Phase 1: navigation) - #495
Draft
Roy (RDMacLachlan) wants to merge 1 commit into
Draft
Restructure TOC by audience (Phase 1: navigation)#495Roy (RDMacLachlan) wants to merge 1 commit into
Roy (RDMacLachlan) wants to merge 1 commit into
Conversation
Reorganize msix-src/toc.yml into seven audience-oriented top-level nodes (Overview and concepts, Develop MSIX apps, Repackage existing apps, Deploy and manage MSIX, Reference, Troubleshooting and validation, Resources) to optimize navigation for the Development, App repackaging, and App Deployment audiences. This is a navigation-only change: every existing article href is preserved (167 distinct hrefs, verified against the previous TOC), no files are moved, and no published URLs change. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 648831a: ✅ Validation status: passed
For more details, please refer to the build report. |
Roy (RDMacLachlan)
marked this pull request as draft
July 11, 2026 18:28
| href: index.yml | ||
| - name: What is MSIX? | ||
| href: overview.md | ||
| - name: MSIX containerization overview |
There was a problem hiding this comment.
That's a pretty high position on the charts for such a topic
| - name: MSIX appContainer apps | ||
| href: msix-container.md | ||
| href: msix-container.md | ||
| - name: Flexible virtualization |
There was a problem hiding this comment.
MSIX containerization overview AND Flexible virtualization get top level topics, and pretty early in the list? Hmm
| - name: MSIX resources | ||
| href: resources.md | ||
| - name: Customer journeys | ||
| - name: Develop MSIX apps |
There was a problem hiding this comment.
Sigh. 15 years and we're still intent to talk about apps and not packages
Develop MSIX packages
or at least
Developer MSIX packaged apps
| - name: App Attach from Visual Studio | ||
| href: desktop/app-attach-from-visualstudio.md | ||
| displayName: Azure Virtual Desktop, App Streaming, Visual Studio, Extension | ||
| - name: Package from the command line |
There was a problem hiding this comment.
Packaging in VS (line 56)
vs
Package from the command line
Inconsistency, bad :P
SUGGESTION:
- Packaging in Visual Studio
- Packaging in the command line
?
| @@ -1,33 +1,22 @@ | |||
| - name: MSIX | |||
| items: | |||
| - name: Overview and concepts | |||
There was a problem hiding this comment.
This was hard to read so I copied everything and and stripped down to just the '- name:' rows here's the structure
MSIX
Overview and concepts
Overview
What is MSIX?
MSIX containerization overview
Features and supported platforms
Features and supported platforms
MSIX appContainer apps
Flexible virtualization
MSIX package signing
Overview
End-to-end signing guide
Sign an app package using SignTool
Sign an MSIX package with Device Guard signing
Known issues and troubleshooting
Unsigned MSIX for testing
App-V versus MSIX
App package formats
Overview
App package architectures
Asset packages
Resource Packages
Resource Packages
Modification packages
API and schema reference
Package Manager API
Packaging APIs
App manifest schema
App Installer file schema
MSIX resources
Customer journeys
Develop MSIX apps
Overview
Key concepts to know before packaging
Overview
DB Systel
ECNO
MID GmbH
SAP
Schneider Electric
Trend Micro
MSIX partners
Prepare to package a desktop app
Understanding how packaged desktop apps run on Windows
Bundling MSIX packages
Packaging in Visual Studio
Overview
Set up your desktop app for packaging in Visual Studio
Package a desktop or UWP app in Visual Studio
Sign packages with Azure Key Vault
Optimize binaries with native images
App Attach from Visual Studio
Package from the command line
Overview
Generating package artifacts
Create an MSIX package with the MakeAppx.exe tool
Create a certificate for package signing
Sign an MSIX package using SignTool
Package creation with the packaging layout
Developing with asset packages and package folding
Sign your MSIX package
Overview
End-to-end signing guide
Sign an app package using SignTool
Sign an MSIX package with Device Guard signing
Known issues and troubleshooting
Unsigned MSIX for testing
MSIX and CI/CD pipelines
Overview
MSIX Packaging Extension
Configure CI/CD pipeline with YAML file
Sign with Azure Key Vault in a CI/CD pipeline
Extend your app
Overview
App extensions
Custom properties for app extensions
Optional packages
Building an app with a modification package
Update your app from code
Update Store-published apps from your code
Update non-Store published apps from your code
MSIX SDK
Overview
How to create an MSIX package on Linux
Use the MSIX SDK to distribute an MSIX package
Release notes
MSIX SDK Release 1.4
MSIX SDK Release 1.5
MSIX SDK Release 1.7
Create an MSIX package from an existing installer
Repackage existing apps
Overview
Know your installer
MSIX partners
Overview
Package a desktop app using third-party installers
Package a desktop app using third-party installers
Set up your environment
Prepare your environment for conversion
MSIX packaging environment on Hyper-V Quick Create
Set up instructions for remote desktop machine conversions
Set up the MSIX Packaging Tool
MSIX Packaging Tool overview
Best practices for the MSIX Packaging Tool
Best practices for the MSIX Packaging Tool
Using the MSIX Packaging Tool in a disconnected environment
Known issues and troubleshooting tips for the MSIX Packaging Tool
Known issues and troubleshooting tips for the MSIX Packaging Tool
Duplicate MSIX Packaging Tool settings across devices
Release notes for the MSIX Packaging Tool
Use the MSIX Packaging Tool
Create an MSIX package from any desktop installer
Conversion with the command line
Edit icons and assets using the MSIX Packaging Tool
Tasks for after you create an MSIX package
Package Support Framework (PSF)
Overview
Support legacy context menus
MSIX Toolkit
Overview
Modify package publisher script
Accelerators
App-V versus MSIX
Build an MSIX package from source code
Overview
Key concepts to know before packaging
Overview
Prepare to package a desktop app
Understanding how packaged desktop apps run on Windows
Bundling MSIX packages
Packaging in Visual Studio
Overview
Set up your desktop app for packaging in Visual Studio
Package a desktop or UWP app in Visual Studio
Sign packages with Azure Key Vault
Optimize binaries with native images
App Attach from Visual Studio
MSIX and CI/CD pipelines
Overview
MSIX Packaging Extension
Configure CI/CD pipeline with YAML file
Sign with Azure Key Vault in a CI/CD pipeline
Package from the command line
Overview
Generating package artifacts
Create an MSIX package with the MakeAppx.exe tool
Create a certificate for package signing
Sign an MSIX package using SignTool
Package creation with the packaging layout
Developing with asset packages and package folding
Extend your app
Overview
App extensions
Custom properties for app extensions
Optional packages
Building an app with a modification package
Manage your MSIX deployment
Deploy and manage MSIX
Overview
Plan for your deployment
Install MSIX with App Installer
App installer user interface
Create custom App Installer UX
Auto-update and repair apps
App Installer Authentication Manager
Install and update the App Installer
App installer security Features
Distribute your MSIX in an enterprise environment
Overview
Microsoft Intune admin center
Microsoft Configuration Manager
Microsoft Intune
MSIX PowerShell Cmdlets
Using Group Policy
Preinstalling packaged apps
Install earlier versions of an MSIX app package
Install and use App Installer
Install MSIX with App Installer
App installer user interface
Create custom App Installer UX
Auto-update and repair apps
App Installer Authentication Manager
Install and update the App Installer
App installer security Features
Deploy MSIX with App Installer file
App Installer file overview
Troubleshoot installation issues with the App Installer file
API issues
Distribute your MSIX in an enterprise environment
Overview
Microsoft Intune admin center
Microsoft Configuration Manager
Microsoft Intune
MSIX PowerShell Cmdlets
Using Group Policy
Preinstalling packaged apps
Install earlier versions of an MSIX app package
Distribute your MSIX through the Web with App Installer
Overview
Distribute a Windows 10 app from an Azure web app
Passing installation parameters to your app via App Installer
Distribute your MSIX in a consumer environment
Overview
Microsoft Store
Shared package container
Create directory based on package app directory
MSIX package updates
Overview
Differential updates for MSIX app packages
Update Store-published apps from your code
Update non-Store published apps from your code
Shared package container
Create directory based on package app directory
MSIX persistent identity
Deploy MSIX Core for Windows 10 1703 and earlier
Deploy MSIX Core for Windows 10 1703 and earlier
Overview
Deploy MSIX Core with Microsoft Endpoint Configuration Manager
Create an MSIX package with MSIX Core from source code
Troubleshooting
Deployment Validation and Troubleshooting
Enforcing Package Integrity check
Reset and Repair MSIX Apps
MSIX validation, testing, and troubleshooting
Reference
Package Manager API
Packaging APIs
App manifest schema
App Installer file schema
Troubleshooting and validation
Overview
MSIX troubleshooting guide
Known issues when packaging an MSIX
Resources
MSIX resources
MSIX partners
Customer journeys
Overview
DB Systel
ECNO
MID GmbH
SAP
Schneider Electric
Trend Micro
I suggest throwing this into Word as an Outline view, or some equivalent tool, so it's easy to collapse and just view the top level, rationalize ordering, then drill down through each
If you just pull out the top level items you get
- MSIX
- Overview and concepts
- Develop MSIX apps
- Create an MSIX package from an existing installer
- Repackage existing apps
- Build an MSIX package from source code
- Manage your MSIX deployment
- Deploy and manage MSIX
- MSIX validation, testing, and troubleshooting
- Reference
- Troubleshooting and validation
- Resources
Some immediate questions come to mind
- Develop MSIX apps
- Create an MSIX package from an existing installer
- Repackage existing apps
- Why is the 2nd bullet not a child of the first?
- How do the 2nd + 3rd bullets differ?
SUGGESTION: Keep 1st bullet and under that create 3: Developing blahblah + Create from existing installer + Repackage. In essence and more simply stated: Create + Convert + Repackage
- Build an MSIX package from source code
Unclear how this differs from the previous bullet. Is this about build tooling? Or this IS the 'Create' bullet I mentioned and should be moved up?
- Reference
- Resources
What's the difference?
Perhaps thinking in terms of the lifecycle would help:
- Design / Create
- Build
- Package
- Test
- Distribute
- Manage
- Support
- Resources
- FAQ
Then create, convert an existing app/installer and repackage neatly fall under #1, and the rest mostly neatly fall under / are 2-9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restructures
msix-src/toc.ymlinto seven audience-oriented top-level nodes to optimize navigation for the three target audiences (Development, App repackaging, App Deployment):Scope & safety
displayNamesearch hints and external?context=/windows/msix/renderlinks are retained.