[docs] Document collapsible dashboard navigation rail - #1631
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
[docs] Document collapsible dashboard navigation rail#1631aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Documents changes from microsoft/aspire#19431 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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
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.
Documents changes from microsoft/aspire#19431
@JamesNKTargeting
release/13.6based on the source PR milestone13.6.Why
PR #19431 migrated the Aspire Dashboard from Fluent UI Blazor v4 to v5. As part of the migration, the PR's "User-facing usage" section calls out that the desktop navigation rail "can now be expanded to show page labels or collapsed to icons, and the selected mode persists across reloads" — a previously undocumented, user-visible navigation feature. The
AspireMenuButton,AspireProgressRing, and other new public dashboard component types introduced by the migration are internal implementation details and don't need separate end-user documentation, but the persisted collapsible nav rail behavior is directly user-facing and worth calling out on the dashboard tour page.What changed
dashboard/explore.mdx, right before the existing "Resources page" section, describing the collapsible desktop navigation rail (icon-plus-label vs. icon-only modes) and noting that the selected mode persists across reloads.Files modified
src/frontend/src/content/docs/dashboard/explore.mdx(updated existing page, no new page created)