I first got really serious about it when we lost the RSS 2.0 spec on a server upgrade at Harvard. That's when I realized that unless we took serious steps to pr

I first got really serious about it when we lost the RSS 2.0 spec on a server upgrade at Harvard. That's when I realized that unless we took serious steps to protect the content, by using least common denominator technology, and not requiring a separate domain, that it wouldn't last very long after everyone who cared about it was gone from Berkman. It's turned out pretty well. The spec is still there and accessible, and now it's been almost ten years at that spot. I'm also hosting my uncle's site and now my father's. I'm not happy with the job I'm doing on either of them, but I have my own work to move forward, and as I do that of course I'm creating MORE problems. But I'm also trying to be mindful of separating the content from the rendering. The actual content is stored pretty permanently, and the rendering is considered lose-able. Eventually I hope to have ultimate editorial flexibility and have it also be very future-safe. CMSes can anticipate these problems, and I've tried to do that in my latest development.