Skip to content

Commit cd7a2e6

Browse files
committed
Fixes
1 parent 6639466 commit cd7a2e6

5 files changed

Lines changed: 9 additions & 386 deletions

File tree

.openpublishing.redirection.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@
33
{
44
"source_path": "hub/apps/design/widgets/widgets-create-a-template.md",
55
"redirect_url": "/windows/apps/develop/widgets/widgets-create-a-template",
6-
"redirect_document_id": true
6+
"redirect_document_id": false
77
},
88
{
99
"source_path": "hub/apps/design/style/sound.md",
1010
"redirect_url": "/windows/apps/develop/ui/sound",
11-
"redirect_document_id": true
11+
"redirect_document_id": false
1212
},
1313
{
1414
"source_path": "hub/apps/design/app-settings/store-and-retrieve-app-data.md",

hub/apps/design/app-settings/guidelines-for-app-settings.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,19 +52,19 @@ If you're using a [command bar](../controls/command-bar.md) or tool bar, place t
5252

5353
The app settings page should open full-screen and fill the whole window. Use a scrollable layout with a constrained max width (around 1000–1100 px) so content remains readable on wide displays. Group related settings under section headers using the **BodyStrong** text style.
5454

55-
Use the [SettingsCard and SettingsExpander](/windows/communitytoolkit/controls/settingscard) controls from the [Windows Community Toolkit](https://aka.ms/toolkit/windows) to build your settings page. These controls provide a consistent, accessible layout with a header, description, icon, and an action control aligned to the right side of the card.
55+
Use the [SettingsCard and SettingsExpander](/dotnet/communitytoolkit/windows/settingscontrols/settingscard) controls from the [Windows Community Toolkit](https://aka.ms/toolkit/windows) to build your settings page. These controls provide a consistent, accessible layout with a header, description, icon, and an action control aligned to the right side of the card.
5656

5757
For complete implementation examples, see the [WinUI Gallery settings page](https://github.com/microsoft/WinUI-Gallery/blob/main/WinUIGallery/Pages/SettingsPage.xaml) and the [Windows Community Toolkit SettingsControls sample](https://github.com/CommunityToolkit/Windows/blob/main/components/SettingsControls/samples/SettingsPageExample.xaml).
5858

5959
![layout for app settings page on desktop](images/appsettings-layout-navpane-desktop.png)
6060

6161
### SettingsCard
6262

63-
Use a [SettingsCard](/windows/communitytoolkit/controls/settingscard) for individual settings. Each card has a **Header**, an optional **Description**, an optional **HeaderIcon**, and an action control (such as a `ToggleSwitch`, `ComboBox`, or `Button`) placed as the card's content. Setting the `IsClickEnabled` property to `true` makes the entire card clickable, which is useful for navigation-style entries.
63+
Use a [SettingsCard](/dotnet/communitytoolkit/windows/settingscontrols/settingscard) for individual settings. Each card has a **Header**, an optional **Description**, an optional **HeaderIcon**, and an action control (such as a `ToggleSwitch`, `ComboBox`, or `Button`) placed as the card's content. Setting the `IsClickEnabled` property to `true` makes the entire card clickable, which is useful for navigation-style entries.
6464

6565
### SettingsExpander
6666

67-
Use a [SettingsExpander](/windows/communitytoolkit/controls/settingsexpander) when a setting has sub-options that should be revealed on demand. The expander shows a primary action control on the header row and additional `SettingsCard` items inside the `Items` collection. This keeps the page compact while still surfacing advanced options. Avoid nesting expanders deeper than one level.
67+
Use a [SettingsExpander](/dotnet/communitytoolkit/windows/settingscontrols/settingsexpander) when a setting has sub-options that should be revealed on demand. The expander shows a primary action control on the header row and additional `SettingsCard` items inside the `Items` collection. This keeps the page compact while still surfacing advanced options. Avoid nesting expanders deeper than one level.
6868

6969
## App theme settings
7070

@@ -113,7 +113,7 @@ Once you have a list of items that you want to include in your app settings page
113113

114114
## Related articles
115115

116-
* [SettingsCard and SettingsExpander (Windows Community Toolkit)](/windows/communitytoolkit/controls/settingscard)
116+
* [SettingsCard and SettingsExpander (Windows Community Toolkit)](/dotnet/communitytoolkit/windows/settingscontrols/settingscard)
117117
* [Command design basics](../basics/commanding-basics.md)
118118
* [Guidelines for progress controls](../controls/progress-controls.md)
119119
* [Store and retrieve app data](../../develop/data/store-and-retrieve-app-data.md)

hub/apps/design/style/sound.md

Lines changed: 0 additions & 156 deletions
This file was deleted.

hub/apps/design/toc.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,9 @@ items:
8484
href: accessibility/designing-inclusive-software.md
8585
- name: Designing a settings page
8686
href: app-settings/guidelines-for-app-settings.md
87-
- name: Design your app for bidirectional text
88-
href: globalizing/design-for-bidi-text.md
89-
- name: In-app help
87+
- name: Design your app for bidirectional text
88+
href: globalizing/design-for-bidi-text.md
89+
- name: In-app help
9090
items:
9191
- name: Guidelines for app help
9292
href: in-app-help/guidelines-for-app-help.md

0 commit comments

Comments
 (0)