What are your reasons for reading my blog?

  1. You like to read about my mistakes? (I hope not)
  2. You think I am funny? (probably not)
  3. You like the color scheme of my blog? (doubtful)
  4. You have nothing else to do at work but look like you are trying to be productive? (possibly)
  5. You like to look at a lot of pictures and hate so much reading? (maybe)
  6. You actually think that some of my content has relevance to the issues you are facing? (quite possibly)
  7. You have not where else to go to get some of your BizTalk issues answered? (probably)
  8. You have an RSS feed to my siteand like Pavlov’s dog, you can’t help but look at the entry that I made? (Most likely)

Wouldn’t it be great if there was one place that you could go to find all of your answers about BizTalk? If there was such a place, what would that place have on it?

Let me give you a list of the things that I have thought of (with some help, which I will talk about later).

  • Little videos off to the side of each feature of BizTalk, when I press the F1 key there is a link to a description and a video of how to use that feature. Of course that video would need to have subtitles because my Alienware does not have enough speakers (actually I don’t want to bug my co workers).
  • Links to brown bag events that have to do with BizTalk.
  • Everything would have two use cases so not only do I have an understanding of what it is I am looking for, but also how it applies in the real world.
  • More pictures (you knowa picture is worth a thousand words).
  • Have the ability for me to choose the topics I am interested in, and upon arriving on the msdn home page, have a list of the pages that have changed, so I can keep abreast of the things I am interested in and what on those pages have changed.
  • More use cases, more real world examples as a note on each of the pages, ex: how can this setting make my life easier?
  • Where is the RSS feed for this page? (Shouldn’t there be one?)

I being up at the SOA conference I had a wonderful raw meat meal with some great members of the documentation team! (If you didn’t know they are great, ask some people who started learning BTS in the prerelease of 2004 and compare the help to what it is now, Webster’s dictionary of great: BizTalk documentation team!) They asked me what I would wish for in the documentation, how it could be better. These are some of the things that I wish were in there. I am a visual guy, I can’t really learn much by reading, I learn more by watching and breaking and then hopefully fixing.

What would you like to see in the documentation, what type of stuff would lead you to the msdn site first instead of google?