Chris Glein

Saw your comment on this PR: https://github.com/geordanr/xwing-miniatures-font/pull/126#issuecomment-926882591 FWIW that version of the font works great for me. Everything seems to be in order, at least to my eyes.

@arunvenkat1911 Can you share the build log that contains the failure?

From that build log: > × Build failed with message Building Solution - error code 1. Check your build configuration. × It is possible your installation is missing required software...

Something in RNW's codepush support is interacting with cppwinrt wrong. Let's follow up with an issue on [that repo](https://github.com/microsoft/react-native-code-push/issues) to make sure it's tracked.

Work is to set up the pipelines to publish these docs automatically. Until this is fixed we have docs that are going nowhere (example: native module docs, React package provider,...

I believe we were slow on documenting IKeyboardEvent because we had some unifying changes still in the works. Although at this point that is more stable. @rectified95 can you look...

Could also edit the table now to include 0.66. Slightly weird without 0.65 out, but also less bad than forgetting this.

FancyMath is nice in that it's simple. But too simple if we don't have examples of more Windows-y stuff, calling real WinRT APIs.

We'll need to gather up content to jumpstart this. There's the Metro troubleshooting page we could use to seed. Could have the script for initializing the tools here. Action is...

There are two troubleshooting pages today: - https://microsoft.github.io/react-native-windows/docs/native-modules-troubleshooting - https://microsoft.github.io/react-native-windows/docs/metro-config-out-tree-platforms Maybe something with content on the wiki? Only page I spotted was [for Metro troubleshooting](https://github.com/microsoft/react-native-windows/wiki/Metro-Troubleshooting-Guide) (so maybe duplicate with the...