Improve Documentation.

[ederbond]

Feature request

Please provide an updated documentation with detailed info about how each operator works.
If possible make create it with marbles grafics like what it's on this website http://reactivex.io/documentation/operators/zip.html
the main issue with the website I've mentioned is that some of of it's methods simple doesn't exists on Rx.NET and there are others that simple doesn't works as described there. I guess a comprehensive documentation would save lots of developers headaches while trying to do things using this framework.

[thundersen]

The readme contains links to:

• An MSDN site from 2011 containing a header that says We're no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported.
• The Intro to Rx site that was made for 1.0
• http://reactivex.io/ where choosing the platform C#/.Net leads back to this repo
• A UI library which I'm not interested in

That's not a great state of affairs in my opinion.

[AndreasPetersen]

I come from Java where I've been using SmallRye Mutiny for reactive programming, so I understand the reactive programming principles well. However, I find the documentation for Rx.NET to be hard to use. From my understanding it's basically only this book? It has a number of problems:

• There's no unified search function on the website. I constantly find myself lost in the book, when I just need to figure out how a specific function works.
• I already understand reactive programming, so I'm not looking to learn that. I'm specifically looking how can I do the things I used to be able to do with Mutiny in Rx.NET.

In comparison the Mutiny documentation is structed according to Diátaxis, which makes it far easier to use the documentation. Specifically I'm looking for guides and reference documentation, where the Rx.NET book mixes all these content types.

Are there any plans to improve the Rx.NET documentation?