Commentary

George Dearing
 

Will Content Management Be Most Affected By Open Source?

Some of open source's biggest proponents were probably gloating this week over some results from North Bridge Venture Partners' annual open source survey (PDF). Most of the findings weren't terribly prophetic, but there were a few that caught my eye.

Some of open source's biggest proponents were probably gloating this week over some results from North Bridge Venture Partners' annual open source survey (PDF). Most of the findings weren't terribly prophetic, but there were a few that caught my eye.Apparently the respondents singled out the content management market as the segment with the highest chance of being turned upside down within the next five years. The drama, however, is well under way, with a cast of thousands being led by companies such as Alfresco, Acquia, and a cottage industry of solution providers pitching Web platforms like Joomla, DotNetNuke, and Drupal.

Throw in the bevy of SaaS providers delivering content capabilities via cloud computing and you've got even more disruption. Will all these choices add up to more confusion for customers? I doubt it. With Web standards continuing to be ironed out and open source business models maturing quickly, companies can go as commercial (read proprietary or on-premise) or open source as they choose without the dreaded vendor lock-in.


More Business Intelligence Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

It's pretty clear that the social Web is driving the demand for open source frameworks and with the mindset of "social publishing" continuing to be on Web agendas everywhere, look for community-led expansion and innovation to accelerate.

Smart companies realize the social part of the Web isn't leaving the party anytime soon and have made their demands clear. They want to be their own media companies, creating and distributing content globally on their own terms. If vendors can't provide the tools, they'll find their own.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links