what's appropriate level of granularity we expect out of examples? I'm constantly wavering between making examples go to the boolintegralfloating point level, or should it go to the value, reference, pointer level?
@JonChan I am having the same thoughts. Or the third option: both. Because we only have a topic and examples level and it might be worth documenting the differences between value, reference etc as well as primitives etc. So probably the name 'C# Types' is a bit to vague.
I feel like the granularity of the documentation in overall is becoming a problem. I already see vague topics (i.e. reflection, generics) with some examples but they are heading toward a bucket of unsorted code.
for now, yeah; after some discussion we decided it makes sense because Examples and Topics aren't really "owned" the same way Q&A post are - we're expecting a lot more long lived pages receiving lots of edits
it won't give you any rep certainly, depending on how rep shakes out we may have to revisit example & topic ownership
On my list are things like fixing the flag count, clarifying the UI to better explain how handling flags works, and looking into when we should show what flags to what people.
I like the idea of "favorites" (perhaps with a better name) similar to Q&A - where we'd show you a list of changes that happened when you visit Docs, but not necessarily spam your inbox with everything
I think we can definitely do something with flag handling based on rep and whatnot. It's hard for us to do per-tag rep, though. It'd have to be overall or we'd have to fall back on using tag badges.
@Sam probably not, they work pretty differently from Q&A suggested edits
Proposed changes in docs are more of a first-class citizen. they are one of the activities one can do within Documentation. It's more analogous to posting a question or an answer, IMO.
Not sure yet. I don't see wiring any of this into the existing review queue system... but if we do, it'd most certainly be as a separate queue - reviewing guidelines/standards for revising docs changes would be different from answer edits, etc.
Before I go ahead and add more examples of operators, I'd like a second opinion on an example I've already written. Are these kinds of examples too "wordy"?
I try to search for foo in the C# documentation. However, the search results escaped the # in the search results after clicking the Request Topic button.
As a moderator, I would expect it to bring up the no-action-needed flag-dismissing dialog. That might be a good place to explain what it actually does.
I just tried to make a fake proposal, with a rather... interesting edit comment. And this happened:
It looks like I managed to end a <script> tag (which is exactly what I was trying to do). This means I could probably start a script tag, which is a bad thing.
I think that http://docs-beta.sta...
I've just been thinking a little more on the rep discussion post; and I've got a few ideas for the system, but I was thinking of separating each idea into its own answer (community wiki'd) to allow the community to individually vote on each proposal. (Rather than just posting a single answer with all my suggestions glued together.) Would that indeed be the better approach?
I try to search for foo in the C# documentation. However, the search results escaped the # in the search results after clicking the Request Topic button.
I just tried to make a fake proposal, with a rather... interesting edit comment. And this happened:
It looks like I managed to end a <script> tag (which is exactly what I was trying to do). This means I could probably start a script tag, which is a bad thing.
I think that http://docs-beta.sta...