1. exporting content w/ context

    Concerns regarding Responsive Web Design persuade prudent solutions towards exporting content; platform agnostic approach to mobile context and also its periphery. Seamless experience can be built only with total reach for every context across most platforms.

    The whispering messengers rise evidently in http://blog.comscore.com/2011/06/facebook_linkedin_twitter_tumblr.html . The content today is not in any search engines mercy, its plain relative reach, social. The consumption mode around these divergent technologies is never defined well. The assumption regarding the present media is biased to each others form.
    Instance: The most important approach to the bookmark policy is still prevalent. Recent blog statistics ( http://blog.zite.com/2011/07/zite-integrates-highly-requested.html ) with the aggregation and the likes, assumed on the <title> element, even with the contextual tag and hierarchy.

    • Two basic form of < title > element to keep context at glance “little visible context”.
    Example: <title>{Title}
    {block:PostTitle} - {PostTitle}{/ block:PostTitle}</title>
    Long tag and archive pages are even more susceptible to get lost without its intended context. This peephole concept is widely prevalent in mobile context and listings like ‘saved’ pages in opera mini. Context is an important element, do your best to save the hassles.

    Reference → http://w3.org/TR/html5/semantics.html#the-article-element http://lukew.com/ff/archive.asp?tag&blogs http://useit.com/alertbox/weblogs.html and http://useit.com/papers/webwriting/