The Salesforce service appears to be down. This outage should have no impact on i-Dialogue hosted sites, but may impact page templates that are dependent on real-time Salesforce data.

We are monitoring the situation closely.
You may monitor the status of this service at http://trust.salesforce.com/ or http://www.trustsaas.com

 

Graham Hill has a thoughtful blog post on Five Challenges that Keep CMOs Awake at Night with some insightful thoughts on the future of CMS software.

Some bullets:
"Marketing is inexorably becoming more decentralised"

I sometimes have to remind myself that the "web" is a reference to it's intrinsic structure and that applying centralized, hierarchical, and org chart models to the web is often the source of some people's stress.

We, as a CMS vendor, make no promises that we can help manage all web content. It's just not possible or practical today. I am, however, passionate about centrally managing all marketing investments and tracking/correlating their responses. CRM mixed with CMS is a good solution for this.

Customer-responsive model.... A model that biological systems have perfected billions of years ago. In this model, broad rules are developed centrally for universal use at touchpoints with customers, which are then interpreted locally in real-time using all the contextual information available.

This is exactly correct, but how does a CMS address this need? Our response is to create languages at a higher level of abstraction than basic HTML and let marketers seed page templates with rule intentions that allow for specific types of dialogues to emerge.

The CMS of tomorrow will be addictive, much like Google, Facebook, or Twitter. Marketers will actively monitor point solutions and rely on the CMS to spot trends in real-time and allow organizations to respond to comments, ratings, and tags.

The concept of 'reports' will gradually disappear and be replaced with real-time 'trends'.

Web Statistics 2.0 will emerge around social metrics. Legacy metrics like impressions, unique visitors, and browser type by region will have decreasing value.

Customer Co-creation is the next big thing.

When websites are effectively configured to support community input, then marketing's ability to "listen" becomes extremely important.

As CMS‘ have grown larger, more integrated, more unwieldy and more expensive, some organisations have responded by going for simpler, leaner, right-sized CMS tools

In designing i-Dialogue 9.0 I've come to several "forks in the road". Should we make a particular feature simpler or add more advanced functionality? Is there a compromise between the two?

For example, the concept of a "discussion forum" is one that should be as simple as adding a <dlog:Discussion /> tag to a page template that let's a thread ensue. But there will be those that criticize that simplicity. The old way of thinking is that you're 'supposed' to deploy a forum as a separate, and often expensive, solution.

There is such a huge gap between what analysts are telling people they need and what companies really want. In economically challenged times you see purchasing committees emerge that are trying to play it safe and manage all possible risk by purchasing a complex CMS system that has been around for several years.

Graham goes on to use Clayton Christensen's "Disruptive Technology" model as a means of understanding next-gen CMS's. If that is the case, then bottom-up adoption of faster, simpler, cheaper solutions are on the horizon.

... is to invent it (to borrow from an Alan Kay quote)

Given that my 2007 and 2008 predictions were too dependent on other people or organizations (don't follow those links. It was painful enough for me to re-read them ), I'm taking a different approach this year and simply "predicting" what's going to happen in 2009 based on variables within our control.

"Year of the Cloud"
I like to think small businesses are a leading indicator of the broader economy, and if that's the case, then 2009 will be a strong year for cloud computing as small businesses move to both produce and consume cloud based services. Future Fortune 500 companies will start in 2009 with SaaS and cloud computing baked into their DNA.

"CRM 2.0 = Community Relationship Management"
"Web 2.0" features, such as democratization, user-generated content, tagging, and rating will find their way into B2B portals and websites. "Social networking" will be a feature of web content management systems, instead of a silo application.

Customers will increasingly want go online and manage the relationship with their suppliers/vendors through their portals.

The job title of "Community Manager" will become common. They'll need tools like the Community Graph to gauge customer demands and needs.

"Browser Is the New IDE"
Web development will increasingly be done with lighter weight tools, such as Firefox and FireBug, allowing for a completely browser-based integrated development environment. Developers will have the agility to access and modify their applications from anywhere in the world using netbooks.

Websites will no longer be seen as being discrete deliverable projects. Instead, websites will become fluid entities that morph and adapt to the clients and organization's needs. The browser IDE will enable this agility.

Visual Studio .NET and Eclipse will remain powerful, essential, yet "old school" tools. The inherent conflict of interest between SaaS and traditional IDE's will result in more browser IDE adoption.

"Useful Metrics"
Online solutions will break away from the legacy of "Business Intelligence" and "Marketing Analytics" and provide real-time metrics that are pragmatic, useful, and actionable.

"Gaming As A Metaphor"
CRM and call center workers will adopt line of business applications much more readily if the user experience is aligned with video game design elements. Responsive, real-time, and graphical UI's will be favored over forms-based applications.

Employees will prefer to "interact" with their customers online in much the same way they interact online in PVP games. Learning curves will be reduced and adoption will increase.

Company goals and missions can be more easily visualized and real-time feedback provided through rich game-like interfaces.

"Collaborative Development"
An extension of the IDE will give web developers direct access to an online repository of pre-built scripts and cloud connectors, from Google Charts and Maps, to Salesforce web to lead forms, and StrikeIron tax services.

Principles of open source and Creative Commons will encourage this "remix" and mash-up of web services to produce new and unique solutions.

"Dynamic Languages"
More than half of all new web development projects will choose to use a dynamic languages, such as Python, Ruby, PHP, or Perl. Browser-based IDEs will accelerate this adoption. Javascript and JQuery will become essential tools for building responsive and interactive web applications.

"Domain Specific Languages (DSL)"
New languages will continue to emerge that are suited for specific tasks and domains. Our own language, Dialogue, will enable web developers and business users to think abstractly about their website/portal/community and easily interact with their online constituents.

"Amazon EC2 Will Rock"
The ease of provisioning an operating system and storage through Amazon and paying for resources based on usage will make EC2 the status quo platform for cloud developers.

"3rd Party Google Apps Get Serious"
Google Apps are at the threshold of being adopted by several organizations, large and small. The only obstacle being industry specific configuration, monitoring, and auditing. 3rd party partner apps will start to move in to help verticalize Google Apps and replace existing email/calendar productivity applications.

It's been several years since I last put together a recording studio, but my project for this holiday has been to cobble, re-purpose, and generally upgrade my setup.

The wife has incrementally reclaimed the home office previously used for home recording, so this is an opportunity to move all the gear into a proper environment and re-build from the ground up (I'm using some space at our business office for this project).

I would like this setup to allow spontaneous recording sessions by just having everything wired and ready to go. This will enable the agile composition and recording process I'm hoping to achieve.

What's decidedly different about the new setup is the availability of cloud storage. Digital recording consumes massive amounts of disk storage, and recording engineers tend to be packrats, hanging on to lots of tracks "just in case" they're needed for future re-mixes.

Amazon S3 now frees my mind and allows the audio packrat in me to infinitely scale archive storage without purchasing more external USB drives.

This setup has 3 levels of storage:
Local: Real-time recording and mixing
External: Samples, loops, sound libraries
Cloud: Deep storage and archiving

Adopting SaaS and cloud computing does not have to be such a grievous process, yet I witness so many people going through the stages below that it makes me wonder how applicable the Kübler-Ross 5 Stages of Grief model may be to this process?

Denial

• "Cloud computing is a re-invention of what we've been doing for years on mainframes"
• "SaaS is just a fad"
• "Host our data offsite? No way! That's not secure. We can manage our data better than anyone else"
• "We've done it this way for years. I see no point in changing now"
  

Anger

• "Why are you singling out my project for replacement by SaaS?"
• "I can install/configure a better [software solution] in-house!"
• "Why is my budget being slashed? That's not fair!"
  

Bargaining

• "Just let me add a couple more hard disks to the Exchange server. That will increase everyone's inbox storage to 2GB per person"
• "We purchased this software on a 5 year ROI plan. Let's just ride it out and wait for the next upgrade. Vendor X says our needs will be met in the next release"
• "Let's just outsource the ongoing maintenance of our datacenter to offshore resources and focus on strategic initiatives in-house"
• "There's an open source solution I'd like to try installing and maintaining in-house"
  

Depression

• "What's the point? Business managers will subscribe to any service they find on the Internet"
• "The whole economy is in the tank. If it's bad for me, it must be bad for everyone"
• "The company is going to die. Why doesn't someone just let me go?"
  

Acceptance

• "I suppose SaaS vendor X really can do this job faster, better, cheaper since that is all they focus on"
• "I can retrain and get certified for SaaS solution X"
• "Technology goes obsolete all the time. This is just the next evolutionary cycle"

Am I missing any other common comments?

A core tenet of i-Dialogue 9 is that all website entities inherit the following social interfaces and behaviors:

• Comment
• Rating
• Tag

Objects integrated with other systems, such as Salesforce.com, automatically inherit these social extensions.

Once a community becomes active on a website, how does this information become actionable for a Product or Marketing Manager? How do you visualize a plethora of comments, ratings, and tags on a website? i-Dialogue 9 solves this problem by providing a graphical analytics application for visualizing the online community.

The community graph is interactive and supports high-level visualization of the community and the ability to zoom in on any entity. Graph nodes are color coded to indicate increased activity or negative ratings.

Graph nodes may be modified or removed (for community moderation).

Graph nodes may be ordered by time (most recent at top), rating (highest rated top to bottom), comments (most commented at top) or tags (most tagged at top).

Internal employees may assign a Task to any entity for follow-up.

Default Social Entities:

• Knowledge Base Article
• Trouble Ticket (aka Case or Issue)
• Discussion Forum / Topics / Post
• Document
• Article (Blog or Webpage)
• User
• Chat

Alerts:
Any user may initiate a 'Watch' anywhere within the object graph hierarchy. A watch results in email notification when any child entity is updated.

Product Roadmap Notes
Technology: Silverlight
Anticipated Release Date(s)
Social entity behaviors= Winter 2009
Community Graph=Spring 2009

• New - Added support for Microsoft AJAX client library
• New - Added Jquery support (requires update to ASPX page templates)
• New - Added JSON support
• New - Added XOSQL (eXtensible Object Store Query Language) support for use in AJAX apps (returns JSON array)
• New - Added 'db' interface to client-side Javascript API for use in AJAX applications
• New - Added 'Find' feature to CMS Toolbar (Searches page meta tags and content)
• New - Added 'Localize' feature to CMS Toolbar
• New - Salesforce ETL Map "Auto-Generate Map" dynamically determines storage type (Text or Image) based on XOS value setting
• New - Added 'Date Picker' control to Dialogue Script library
• New - Dialogue Script editor uses client-side Preview and Asynchronous Save (no server postbacks)
• New - Portal Registry Key 'Scripting.DefaultEditor' for using FCK or plain textarea editor

• Changed - Outbound emails set Return-Path to i-Dialogue NDR processing service. Reply-To set to email sender (previously Reply-To set to NDR service).
• Changed - Index optimizations to object store. Enforced use of BLOB storage for strings > 450 characters
• Changed - Disabled late-bound cache invalidation during Salesforce ETL and OM handler (was beta release. Withdrawn and deferred to Jan '09)

• Fixed - Improved caching of generic object collections. Thread safety changes.
• Fixed - Resolved issue preventing Live Chat ETL process to execute when Web Event custom object is not installed in Salesforce
• Fixed - Resolved ETL Map Local Object display issue (one-off index for certain object types)
• Fixed - Improved exception handling in Contact ETL when Account or Account Type not available (related to cascading role inheritance feature)

Salesforce.com announced support for Google Apps Engine (GAE), which is a cloud-based platform for developing websites and portals using Python.

Between GAE, Dialogue Script, and the Salesforce/Plone project, there certainly is a lot of love going around for creating sites with Python.