@KevinMontrose is it really a good idea to put Ninject in .NET documentation? Personally I don't recommend putting out of scope stuff in the .NET framework. Ninject is not the topic of being documented. This beta is about forming a strategy as well. I think putting stuff temporarily at .NET is just confusing and invites others to use it as a general umbrella as well.

I do think we should not stop people in their enthusiasm. Can we build a temporary umbrella next to C#, Dapper and .NET? I am curious how stuff like design patterns, IoC containers will evolve in the docs.

I'm not clear if I have to publish my selected change or if it is already available for review

@KevinMontrose Yes please, I was looking just for something like that: draft it, then share it for comments and feedback.

Even though it is probably really useful only now, while we are all still figuring out how to build and use it!

interesting case in the review process -- I made a change which had a comment -- based on the comment I made another change. This change got rejected because it varied to much from my first change (which I guess the rejector did not read). I've made another change for review. But it makes me wonder... how can I respond to this "train" of comments. It does not seem I can.

(stuff happened here -- esp. if indexers were accessing "base" data - docs-beta.stackexchange.com/documentation/.net/45/dictionaries)

I can foresee a potential problem with topics that are extremely broad, like LINQ (mentioned in chat earlier). My expectation is that each topic answers a very specific question: "How do I use X?" But the LINQ page answers "How do I use every feature in X's tag?" As a ridiculous extreme, would the home topic for .NET include an example of every method and every property in every BCL class? I'm trying to think of a strategy to recommend for this...

Hm. I see the topic request for Strings [docs-beta.stackexchange.com/documentation/.net/topic-requests/…, asking "How are strings handled in .NET? What does "intern'ing" a string mean? How is mutability handled?" Great questions, but they require text explanations, not examples (of how to use String class/objects). Am I missing something?

(link without extraneous ] ): docs-beta.stackexchange.com/documentation/.net/topic-requests/…

I'll put my thoughts into the questions page. No need to discuss here.