I think the better way of doing forwards/backwards navigation is to use a<RootFrame> in the window rather than settingWindow.Content directly.

One pitfall that might make it hard to use the RootFrame's built-in navigation stuff is that I don't think it lets you instantiate the Window types yourself - which makes it hard to get a ViewModel in there.

In the TrayWindow code in my PR, I ended up just settingRootFrame.Content directly because of this limitation (and because I don't need forwards/backwards navigation). But if you could get that working it'd be more idiomatic I think

I switched it to using a Frame so we're not just touching the window content directly, but I'm not using the forward/backwards functionality yet because of the aforementioned issue.

In the future if we solve it, we could have the "Coder Desktop" text and the navigation buttons be on the Window itself, rather than in each page.