Chris Glein

Goals: * Needs to be discoverable from the website (independent of whether it exists on the website) - dedicated page, resources links * Low barrier to update for engineers *...

Fix could be to only allow running one publish at a time.

Makes sense as these are divorced from the normal versioning process. Would be good cleanup.

Do we know what the current requirements are? We'll want to keep the number reasonably up to date, so maybe build in a buffer. May overlap with #156.

The arguments are documented here: https://microsoft.github.io/react-native-windows/docs/getting-started#install-the-windows-extension Do we need more?

Sounds like we have API documentation, but not usage documentation. Clarification could be had around `EmitJsEvent` (tied to a JS event emitter) and `DispatchEvent` (tired to a View) and 'CallJsFunction'...

Also worth answering what exists in core and what documentation exists there.

> To me this is by design, per discussion in #267 By which you mean that TodosFeed should suffice? It isn't minimal, and has been locked in time to match...

These are pretty core to writing a module so this seems higher priority relative to some of the less common stuff.

> some features are only available in some OS versions (we capture some of this but not exhaustively, e.g. animations only work on RS5+) We need to make this discoverable...