Dotnet-api-docs: MSDN Examples always feel like over-executed challenges.

[laserbeak]

Why can't you just start with a simple example and then move onto something more "cool and clever"?
MSDN documentation is the only documentation I use that feels like a challenge. I just want to know how something works, not decipher your over-complicated examples....

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: dc60ab93-74c9-2404-67dd-1dc9017c0dc9
• Version Independent ID: feaee2f1-85dc-7793-b693-853e95f54f39
• Content: String.TrimStart Method (System)
• Content Source: xml/System/String.xml
• Product: dotnet-api
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[mairaw]

Thanks, that's a good suggestion @laserbeak. I'm adding this to our backlog and to our community collaboration project.

[jmarkman]

I'm not sure if this issue is going to be relegated to just the TrimStart method or if this is the groundwork for a larger effort, but I wouldn't mind tackling this if I know the requirements. Would this need to be in all four languages (C#, VB.NET, F#, C++)?

[tannergooding]

@mairaw, given how broad this is, I take that this is marked "up for grabs" in the sense that, if someone sees an example they feel could be improved, they should feel empowered to submit a PR making it better and link back to this issue, rather than needing to open a new issue first, correct?

If that is the case, it might be good to indicate as such for some of our larger issues like this (that are more tracking for a general concern, rather than something that is individually actionable all at once).

[mairaw]

Hi @tannergooding and @jmarkman, you make a good point. The comments are generic enough that could apply to any API work that we do and we should always keep in mind that when writing API reference. But this issue in particular I'd say is for the TrimStart method and we usually try to do at least C# and VB. But if you're not comfortable if one of the languages, just note that and we can add the other one.

But folks should always feel free to add new or simplify samples that overly complicated and just open a PR. If they wanna make sure their work would be accepted, I'd open an issue to discuss with us first.

So let's focus this one on TrimStart, but this is a guidance we should always apply to our content.