202416 Resource 76407 24 24 1209392015163 1209393687379 Controlled Blog Durability -- Is Your Blog Content Sustainable?

Very few people think about their blog content or blog architecture in the context of durability but like anything you build, it's a future success factor.

<p>A blogsite (like a Lexus) is durable. </p><p>Very few people think about their blog content or blog architecture in the context of durability. When I mention it to people they say --</p><blockquote dir="ltr" style="MARGIN-RIGHT: 0px"><p><em>&ldquo;What? How can you wear out your blog?&rdquo; </em></p></blockquote><p>Understanding blog and content durability requires a deeper understanding of the likelihood of future changes that would constrain or otherwise obsolete your content. </p><p>There&rsquo;s no question there will be future innovations that will render the way blogs work today, as obsolete in a future context. <em>Durable blogs</em> will possess attributes that allow them to transform and reshape themselves with little effort. Non-durable blogs will require complete rethinking, rewrites and reformatting of large portions of content and application code bases; non-durable content will require significant reshaping to migrate into new use cases. </p><p>MyST Blogsite&reg; was built on a platform of agile XML and XSLT services that are completely unrelated to blogging or blog architectures. We provide an advertorial platform based on sound information architecture design.</p><p>One example of content durability is how we meld Captyx components into your posts. My hunch is that not a single MyST Blogsite&reg; customer has recognized that Captyx components (such as embedded videos) do not display in RSS feeds. This is intentional and done so for many reasons &ndash; far too complex to go into in this post. But the behavior is critical to creating and managing a durable content system because it makes it possible to create, manage, and integrate content items with (and without) embedded objects. </p><p>This agility is critical to future requirements that have not [yet] been invented. Imagine the day comes when you have 10,000 posts and you suddenly need to utilize your content in ways that heavy objects (such as video components) are not able to be included. Your competitors (who have embedded video code directly into their content) will not be able to participate in such a new use case without significant friction &ndash; they are busy creating non-durable content that assumes all objects in a post must be included in that post regardless of the use case.</p><p>Examples of durability abound in MyST Blogsite&reg; - from the native MyST-ML [XML] markup language available universally across the platform, to the URL-based XML API from which a variety of XML formats can be accessed. In between we find filter patterns that allow you to scope RSS feeds and subsets of your content as HTML, Topic Cloud, which dissects all keywords into a relational map to your posts, and Link Properties that can exist as reference bibliographies in HTML or free-standing syndication feeds. MyST Blogsite&reg; is designed with one assumption - change is coming. ;-)</p> 9 application/xml false blog durability Captyx content durability embedded objects I do not believe you can create a durable information architecture without knowing and understanding the content, the users' interaction with the content as both creators and seekers and the context(s) in which the content is used. http://argus-acia.com/people/bliss_profile.html "agility" Topic Cloud for MyST Blogsite http://blogsite.com/topics/agility My hunch is that not a single MyST Blogsite® customer has recognized that Captyx components (such as embedded videos) do not display in RSS feeds. This is intentional and done so for many reasons ... Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Dosware Team Internet Browser; .NET CLR 1.1.4322; .NET CLR 2.0.50727) 127.0.0.1 127.0.0.1 bfrench 76.120.48.245 false true false false true 174050 false false true false false false true 76407 blog blogsite/Blogsite/web