warnings, TODO!s

Author: zadjii

hub/powertoys/command-palette/add-top-level-commands-to-your-extension.md

@@ -51,7 +51,7 @@ There you have it. Now you can add additional top-level commands to your extensi
 
 If you'd like to update the list of top-level commands dynamically, you can do so in the same way as you would update a list page. This can be useful for cases like an extension that might first require the user to log in, before showing certain commands. In that case, you can show the "log in" command at the top level initially. Then, once the user logs in successfully, you can update the list of top-level commands to include the commands that required authentication.
 
-Once you've determined that you need to change the top level list, call [`RaiseItemsChanged()`](../microsoft-commandpalette-extensions-toolkit/commandprovider-raiseitemschanged.md) on your `CommandProvider`. Command Palette will then ask for the top-level commands via `TopLevelCommands()` again, and you can return the updated list.
+Once you've determined that you need to change the top level list, call [`RaiseItemsChanged()`](./microsoft-commandpalette-extensions-toolkit/commandprovider_raiseitemschanged.md) on your `CommandProvider`. Command Palette will then ask for the top-level commands via `TopLevelCommands()` again, and you can return the updated list.
 
 > [!TIP]
 > Create the `CommandItem`s for the top-level commands before calling `RaiseItemsChanged()`. This will ensure that the new commands are available when Command Palette asks for the top-level commands. This will help keep the work being done in call to `TopLevelCommands()` method to a minimum.

hub/powertoys/command-palette/command-results.md

@@ -47,7 +47,7 @@ If you don't know what else to use, this should be your default. Ideally, users
 
 This result displays a transient desktop-level message to the user. This is especially useful for displaying confirmation that an action took place when the palette will be closed. 
 
-Consider the [CopyTextCommand](../microsoft-commandpalette-extensions-toolkit/copytextcommand.md) in the helpers - this command will show a toast with the text "Copied to clipboard", then dismiss the palette. 
+Consider the [CopyTextCommand](./microsoft-commandpalette-extensions-toolkit/copytextcommand.md) in the helpers - this command will show a toast with the text "Copied to clipboard", then dismiss the palette. 
 
 By default, [`CommandResult.ShowToast(string)`](./microsoft-commandpalette-extensions-toolkit/commandresult_showtoast_string.md) helper will have a `Result` of `CommandResult.Dismiss`. However, you can instead change the result to any of the other results if you want. This allows you to display a toast and keep the palette open, if you'd like. 
 

hub/powertoys/command-palette/creating-an-extension.md

@@ -51,16 +51,17 @@ ExtensionName/
 From here, you can immediately build the project and run it. Once your package is deployed and running, Command Palette will automatically discover your extension and load it into the palette. 
 
 > [!TIP]
-> Make sure you deploy your app! Just **build**ing your application won't update the package in the same way that deploying it will.
+> Make sure you _deploy_ your app! Just **build**ing your application won't update the package in the same way that deploying it will.
 
 > [!WARNING]
 > Running "ExtensionName (Unpackaged)" from Visual Studio will not **deploy** your app package.
 > 
-> If you're using `git` for source control, and you used the standard `.gitignore` file for C#, you'll want to remove the 
+> If you're using `git` for source control, and you used the standard `.gitignore` file for C#, you'll want to remove the following two lines from your `.gitignore` file:
 > ```
 > **/Properties/launchSettings.json
+> *.pubxml
 > ```
-> line from your `.gitignore` file. This file is used by WinAppSdk to deploy your app as a package. Without it, anyone who clones your repo won't be able to deploy your extension.
+> These files are used by WinAppSdk to deploy your app as a package. Without it, anyone who clones your repo won't be able to deploy your extension.
 
 You should be able to see your extension in the Command Palette at the end of the list of commands. Entering that command should take you to the page for your command, and you should see a single command that says "TODO: Implement your extension here".
 

hub/powertoys/command-palette/publish-extension.md

@@ -23,15 +23,28 @@ The following tools are required to build and publish your extension:
 
 Publishing packages to WinGet is the recommended way to share your extensions with users. Extension packages which are listed on WinGet can be discovered and installed directly from the Command Palette.
 
-For the most part, following the steps on [Submit packages to Windows Package Manager](https://learn.microsoft.com/en-us/windows/package-manager/package/) will get your extension onto WinGet itself.
+For the most part, following the steps on [Submit packages to Windows Package Manager](../../package-manager/package/manifest.md) will get your extension onto WinGet itself.
 
 Before submitting your manifest to WinGet, you'll need to check two things:
 
 ### Add `windows-commandpalette-extension` tag
 
+Command Palette uses the special `windows-commandpalette-extension` tag to discover extensions. Make sure that your manifest includes this tag, so that Command Palette can discover your extension. Add the following to each `.locale.*.yaml` file in your manifest:
+
+```yaml
+Tags:
+- windows-commandpalette-extension
+```
+
 ### Ensure WindowsAppSdk is listed as a dependency
 
-If you're using Windows App SDK, then you'll need to make sure that it is listed as a dependency of your package
+If you're using Windows App SDK, then you'll need to make sure that it is listed as a dependency of your package. Add the following to your `.installer.yaml` manifest:
+
+```yaml
+Dependencies:
+  PackageDependencies:
+  - PackageIdentifier: Microsoft.WindowsAppRuntime.1.6
+```
 
 If you're not using the template project, then this may not apply to you. 
 

hub/powertoys/command-palette/samples.md

@@ -25,9 +25,9 @@ class MyCommand : Microsoft.CommandPalette.Extensions.Toolkit.InvokableCommand {
         Icon = new("\uE945"); // Segoe UI LightningBolt
     }
 
-    // Open MY_WEBSITE_URL in the user's default web browser
+    // Open GitHub in the user's default web browser
     public ICommandResult Invoke() {
-        Process.Start(new ProcessStartInfo("MY_WEBSITE_URL") { UseShellExecute = true });
+        Process.Start(new ProcessStartInfo("https://github.com") { UseShellExecute = true });
 
         // Hides the Command Palette window, without changing the page that's open
         return CommandResult.Hide();
@@ -37,7 +37,69 @@ class MyCommand : Microsoft.CommandPalette.Extensions.Toolkit.InvokableCommand {
 
 ## Create a page of commands
 
-TODO!
+```csharp
+using Microsoft.CommandPalette.Extensions.Toolkit;
+
+class MyPage : ListPage {
+    public MyPage()
+    {
+        Icon = IconHelpers.FromRelativePath("Assets\\StoreLogo.png");
+        Title = "My sample extension";
+        Name = "Open";
+    }
+    
+    public override IListItem[] GetItems()
+    {
+        return [
+            new ListItem(new OpenUrlCommand("https://github.com"))
+            {
+                Title = "Open GitHub",
+            },
+            new ListItem(new OpenUrlCommand("https://learn.microsoft.com"))
+            {
+                Title = "Open Microsoft Learn",
+            },
+            new ListItem(new OpenUrlCommand("https://github.com/microsoft/PowerToys"))
+            {
+                Title = "Open PowerToys on GitHub",
+            },
+            new ListItem(new CopyTextCommand("Foo bar"))
+            {
+                Title = "Copy 'Foo bar' to the clipboard",
+            },
+        ];
+    }
+}
+```
+
+## Icons
+
+Icons using the [`IIconInfo`](./microsoft-commandpalette-extensions/iiconinfo.md) class can be specified in a number of ways. Here are some examples:
+
+```csharp
+
+using Microsoft.CommandPalette.Extensions.Toolkit;
+
+namespace ExtensionName;
+
+internal sealed class Icons
+{
+    // Icons can be specified as a Segoe Fluent icon, ...
+    internal static IconInfo OpenFile { get; } = new("\uE8E5"); // OpenFile
+
+    // ... or as an emoji, ...
+    internal static IconInfo OpenFileEmoji { get; } = new("📂");
+
+    // ... Or as a path to an image file, ...
+    internal static IconInfo FileExplorer { get; } = IconHelpers.FromRelativePath("Assets\\FileExplorer.png");
+
+    // ... which can be on a remote server, or svg's, or ...
+    internal static IconInfo FileExplorerSvg { get; } = new("https://raw.githubusercontent.com/microsoft/PowerToys/refs/heads/main/src/modules/cmdpal/Exts/Microsoft.CmdPal.Ext.Indexer/Assets/FileExplorer.svg");
+
+    // Or they can be embedded in a exe / dll:
+    internal static IconInfo FolderIcon { get; } =  new("%systemroot%\\system32\\system32\\shell32.dll,3");
+}
+```
 
 ## Related content