Web Site of Rajiv Pant

Content on Web sites should be managed using systems that were designed from the ground up for the Web. Traditional content management systems with a legacy of features and workflows used for paper-based print products like newspapers and magazines are unsuitable for Web sites. The future of news media content management for Web sites is in:

• simple & quick workflows
• blogs & wikis as the main content types for text
• social networking & community publishing

simple & quick workflows

Complex editorial workflows make sense for print products (on paper) , where once the edition is done, the content and presentation state is “locked” and sent to the presses. Working with Web content writers and editors over the past decade, I have learned that simple, quick workflows are preferable for Web sites. Many Web site producers who hail from print backgrounds now share the same conclusion that complex content management is a hindrance to successful Web site production.

The concept of an edition of the entire product is not necessary for a content Web site. The atomic unit that can be managed and published together can be a package of articles and multimedia or even just one article. A Web site is a living, dynamic, ever changing collection of content where individual items can be updated whenever required or desired or even automatically based on usage.

To be competitive, content needs to be updated and published quickly. Corrections can be made anytime. Thus for Web sites, the editing and approval process should be streamlined and quick all the way from authoring to posting on the site.

A new concept

The ability of online word processors like Google Docs or WriteWith to enable multiple people to edit a document simultaneously and collaboratively is different paradigm from traditional check-in/check-out access control.

blogs & wikis as the main content types for text

Content management system (CMS) which offers the simplicity of blogs and are extensible via plug-ins to add functionality like WordPress or MovableType, make good foundations of a CMS for a news media Web site.

For revisions, editing history and access control, wiki software works well. WikiPedia and WikiNews, which are powered by the MediaWiki software are two good examples.

The concept of content management systems that combine the agility of blogs and editorial control of wikis is interesting to follow. The term bliki seems to be the leading classification of such products.

In many newsrooms, writers are increasingly using blog posts to publish news articles instead of their enterprise-class content management systems. When asked why, they reply because it is simpler and quicker and they don’t need the overhead of things like complex approvals, advanced version tracking and access controls.

social networking & community publishing

Managing content using a blog or wiki is social networking and community publishing activity. On the readership side, successful social news sites like Digg and Reddit have accelerated the evolution of journalism and readership habits towards the social/community model. The distinction between authors and readers itself is blurring with wikis and comments on blogs.

Social networking features are being added to a variety of Web sites. Going forward, expect to see social networking and community features in content management systems.

Conclusion

Media companies should move to using CMS products that prefer simplicity over complex editorial workflows which were a legacy of writing and editing for print products. A news item, story or blog post should be the same content type. It is likely that blogging products that have proven so successful in empowering talented individuals in competing with large companies will evolve into content management systems with the addition of wiki functionality.

My journalist colleagues at Wired.com published some of my comments related to Amazon S3.¹ Wired also posted another article titled Customers Shrug Off S3 Service Failure. I agree with the views of many of the customers expressed in the article. Don MacAskill, CEO of the popular photo hosting site Smugmug, wrote an understanding post about it.

My entire career working for media companies, I’ve held firm the belief that the uptime, reliability, performance, scalability, performance and security of commercial Web sites is of paramount importance. When sites that I’ve been responsible for have had issues, my colleagues and I have given our personal time and energy to resolution. With my teams, I spend considerable time on proactive measures. In my jobs, I’ve had the honor of working closely with and learning from some who do an excellent job running technology operations.²

Experience has taught that things can and sometimes do go wrong. Sometimes calculated risks don’t pan out. Sometimes mistakes cause problems. We are human. We should strive for perfection; we can get close to it, but not fully attain it. We should be prepared for such scenarios. When they happen, we should work diligently and expeditiously on resolution and have frequent and honest communications with stakeholders and customers. Such communications during the incident should include:

• Current status
• What is the full impact?
• Estimated time to resolution
• Any recommended workarounds until resolution, if practical
• Assurance that it is being worked on
  • It often helps to mention who all are working on it and what they are doing

The post-incident communications to stakeholders and customers should include:

• Summary
• What happened, how and why it happened?
  • Including full description of all impact
  • Do not blame³ third-parties or say things like “beyond our control”. A technology leader takes responsibility equally for both insourced and outsourced products and services.⁴
• How it was resolved
  • If the resolution is temporary or long-term
• Next steps
• Plan for eliminating or minimizing this and similar incidents from happening again
• Thank all those who helped resolve and the customers for their understanding
  • Specify any ‘make goods’ or returns you plan to make to the customers, if appropriate

Stakeholders and customers here refer to internal customers of the technology operations team (e.g. the concerned folks in editorial, marketing, sales, finance, legal and other departments). External communications to the public Internet should be handled in consultation with legal and public relations.

S3’s outage (or any outage) isn’t to be taken lightly, but I have faith Amazon and their customers will learn from it.

Disclaimers:

• As explained in the terms of use of this site, any opinions expressed on my personal Web site do not reflect those of any employer, past or present. My Web site and I in my personal life neither represent nor speak for any corporation.
• I have no affiliation, financial or otherwise with Amazon.com. I happen to be a user of their products and services, some of which I like and some that I don’t.
• Personal Web sites like this are exempt from the performance requirements of corporate Web sites My personal Web site is for expressing, learning and R&D. It also happens to be hosted on Amazon EC2 and S3.

1. Silicon Alley Insider and ValleyWag have amusing spins on it. [↩]
2. E.g. Some very talented and accomplished technology operations leaders including Bob Pick, Jamie Gerdes (now at Google), Mark Cox, Chris Jennewein, Patrick Carter, Rocky Vienna and Sharon Mandell. [↩]
3. There may be extreme instances, especially when criminal activity or malicious wrongdoing was the cause where it would be appropriate to blame someone. [↩]
4. It is ok to name service providers  or mention external events for explaining what happened, but don’t do it in a “it was their fault, not ours” tone. The technology leader should factually describe what happened and take responsibility. [↩]

If you already know what the Social Graph API and XFN are, you can skip the background information and go directly to the Blogroll Links plugin for Wordpress that is designed to work with these.

Social Graph API

Google recently announced the Social Graph API.¹ From Google’s Code site:

With so many websites to join, users must decide where to invest significant time in adding their same connections over and over. For developers, this means it is difficult to build successful web applications that hinge upon a critical mass of users for content and interaction. With the Social Graph API, developers can now utilize public connections their users have already created in other web services. It makes information about public connections between people easily available and useful.

We [Google] currently index the public Web for XHTML Friends Network (XFN), Friend of a Friend (FOAF) markup and other publicly declared connections. By supporting open Web standards for describing connections between people, web sites can add to the social infrastructure of the web.

The Google Code site also has a video introduction to the open social graph:

The Google Code site has some interesting example applications. To see the power of the open social graph, follow these links:

• Connections between my URLs on my sites and my pages on social networking sites.
• Connections with some of my contacts found via social networks and sites that are friendly to the open social graph.

All I did was enter my home page http://www.rajiv.com/ into these applications and got the results linked to above.

XHTML Friends Network, a component of open social networks

XFN (XHTML Friends Network) is a simple way to represent human relationships using hyperlinks. In recent years, blogs and blogrolls have become the fastest growing area of the Web. XFN enables web authors to indicate their relationship(s) to the people in their blogrolls simply by adding a ‘rel‘ attribute to their <a href> tags, e.g.:

<a href="http://www.rajiv.com/" rel=”friend met”>Home Page: Rajiv Pant</a>

The above link means that the page at http://www.rajiv.com/ belongs to a friend of the person who who owns the page this link is placed on. The met tag specifies that the two friends have met in real life. The link above would not be placed on a page owned by Rajiv Pant. It would be placed by a friend on their page, for example, on http://www.paradox1x.org/

Here is another example:

<a href="http://photos.rajiv.com/" rel=”me”>Photo Albums: Rajiv Pant</a>

This link states that the page at the URL http://photos.rajiv.com/ belongs to the same person who owns the page this link is placed on. For example, the above link would be placed on http://www.rajiv.com/ telling the Web that the URLs http://photos.rajiv.com/ and http://www.rajiv.com/belong to the same person.

To find out how to write and use XFN, or to write a program to generate or spider it, visit the XFN Web site.

Blogroll Links Plugin for WordPress

For people who maintain their Web site or blog using the WordPress blog content management system, I created an open source plugin called blogroll-links that uses WordPress’ built-in Blogroll feature² and presents links to friends’ home pages and own pages on social networking sites using XFN in the links.

Features of this plugin

• It can show the links by category in blog posts and WordPress Pages.
• It uses WordPress’ standard built-in Blogroll links database. There is no hassle of another list of links to maintain.
• It can be used to show only the links assigned to a particular category, by stating the category slug as defined in that category’s setting in Wordpress.
• It honors the Show/Hidden setting as defined for each link in WordPress.
• It displays the link in the same window or new window, as specified for each link in WordPress.

See this plugin in action

• http://www.rajiv.com/friends/
  • The two lists, first one of links to my own pages on various social networking sites and the second one of links to some of my friends’ pages are generated by this plugin. Yes, those social networks’ logo pictures are also taken by the plugin from the WordPress standard Blogroll links. Code:
  • <h3>My Pages on Social Networking Sites</h3>
<!--blogroll-links category-slug="rajiv-web" sort-by="link_name" sort-order="desc"--><!--/blogroll-links-->
<h3>Web Sites of Some People I Know</h3>
<!--blogroll-links category-slug="people" sort-by="link_name" sort-order="desc"--><!--/blogroll-links-->
• http://www.rajiv.com/charity/
  • This list of charitable organizations with brief descriptions is generated by the plugin. Code:
  • <!--blogroll-links category-slug="charity"--><!--/blogroll-links-->
• http://www.rajiv.com/blog/2004/08/02/search-engines/
  • This list of search engines is maintained as Blogroll links in WordPress. Code:
  • <!--blogroll-links category-slug="search-engines"--><!--/blogroll-links-->
• http://www.rajiv.com/
  • The featured links shown under the “What’s featured here?” section shows the links I’ve categorized as featured in WordPress’ Blogroll links. Code:
  • <a title="featured" name="featured"></a>
<h2>What's featured here?</h2>
<!--blogroll-links category-slug="featured" sort-by="link_name" sort-order="desc"--><!--/blogroll-links-->

Download & install plugin

• You can download and install blogroll-links from the Wordpress Plugins Directory.

1. WikiPedia article explaining what an API, or application programming interface is. [↩]
2. It does not make you maintain yet another list of links [↩]

Over the past 15 years, as the Web has evolved, the web sites have gone through these generations. What’s likely to be next in the future of what the Web will be? This article describes the Web so far and what form it will likely assume.

• 1993-1997: Generation 1.0
  • These web sites can essentially be considered digital versions of printed newspapers, magazines and books.
  • Like with the printed products, the consumer is primarily a reader and interactivity is generally limited to filling out and submitting forms.
  • Content and design are the most important part.
  • Product = Content + Design
  • Examples: Most news and other content sites in the 1990s.
• 1997-2004: Generation 1.5
  • These web sites are similar to what interactive CD-ROM based software used to be in the 1990s.
  • The consumer is a user (as in user of software). There can be significant interactivity between the web site and the user. Interactivity between users is generally limited to discussion boards and marketplace activities.
  • Product = Technology + Content + Design
  • Examples: Online multimedia sites, online gaming sites.
• 2004-present: Generation 2.0
  • The concept of user-submitted-content grows stronger. Users in the virtual community of the site publish, share and view photos, videos and text.
  • The consumer is a community participant.
  • Product = People (User Community) + Technology + Content + Design
  • Examples: YouTube, del.icio.us, Wikipedia
• 2006-future: Generation 3.0 (prediction)
  • Concept of user-submitted-interactivity / user-submitted-programming arises. The users create, own, sell, share, alter and use interactive objects in the virtual environment.
  • Consumers are co-developers.
  • Product = Community Developed Interactivity + People (User Community) + Technology + Content + Design
  • Examples: Virtual environments and ecosystems like Second Life and Kaneva.