New "sub-blog" at weblogs.asp.net
I spent the last few days trying to decide how this was going to work. I want to post at weblogs.asp.net, I mean I’m just one path away from the likes of ScottGu, Roy Osherove, and Eilon Lipton. Not that it makes my blog content any better, but maybe I can improve by osmosis? However I don’t want anything to change about http://www.aaronlerch.com/blog/ – that feeds my ego too much to abandon. (Kidding)
I considered orphaning aaronlerch.com and “starting fresh” at weblogs.asp.net – another great thing about using a service like FeedBurner is that it makes moving my feed around seamless, regardless of whether a new host supports 301 redirects or not. If for some reason weblogs.asp.net “went away” (or something), I could resume posting at aaronlerch.com without any trouble, just a lot of lost content.
What I finally settled on will work the best, I think. I’m going to cross-post between the two blogs. Cross posting–where a post to one blog is automatically posted on another blog via the MetaWeblog API (XML-RPC)–actually offers a complete answer. I want all my content to be available on aaronlerch.com, but I want some of my content to be available on weblogs.asp.net (my best stuff, and technical only).
Here’s where Windows Live Writer makes this very easy on me. I simply select the destination blog in a drop-down and my editor updates in real time, persisting all my content. Way to go WLW team.
I debated having a single RSS feed – pointing to aaronlerch.com, but in the end decided against it. If people are interested in my weblogs.asp.net blog (which, again, will be a subset of aaronlerch.com) they shouldn’t have to suffer through posts like this in the RSS feed. This makes things a little more fragmented than I’d prefer, but I’ll get over it.
What does this mean for you? Nothing! Same great content, same funny style (*cough*). Thanks for listening!