I’ve been throwing around some ideas within my team on how to reach our SMB (Small and Medium Business) IT Pros in the same way that sites like gotdotnet.com reach our developer community.   More specifically, what types of tools can I provide from the windows team that IT Pros can really use and build on? 


Some background: IMHO, the beauty of gotdotnet and other developer sites are the samples.  Samples that are well documented that don’t over complicate a task by overloading the code with error checking and performance enhancements that obscure the readability of the code.  


Does that mean error checking and perf aren’t important? Of course not but error checking might better be handled in a separate sample where I can digest the topics in bite size chunks.


My idea is to publish a site.  Yes! Another site but with a different paradigm; one that doesn’t strive to provide everything to everyone.  More simply, a site with samples that SMB IT Pros can consume with instant gratification.   The key to being successful would hinge on NOT providing everything that everyone needs.  I want to be the local grocer; not that super-value-outlet-mart that I can never find the soup isle in.   By keeping it reasonable I would be able to keep content discoverable.


What type of information would I keep on it? 


Here are a couple ideas I have:


1.)    Script Samples: Boiling down useful WMI and command line scripts to their basic elements for IT Pro that aren’t scripting gurus.   

2.)    Solution guides:  Simple, practical, and applicable guides for implementing windows client and server technologies like DNS 101, DHCP for Beginners, How to move from NT Domains to Active Directory in 10 easy steps. 

3.)    Partner workspaces or forums where the SMB communities can answer questions about documentation on the site in real time.   I can’t stay up as late as I used to anymore.


I’m probably going to make this my holiday vacation project this year to see if I can’t reduce some of the frustration I saw and felt in a previous life as an IT Pro for a university where I didn’t have a supporting staff that already had figured this stuff out. 


Any ideas are appreciated. 


Mike Langowski