Offline processing

• These systems pre-process all content, applying templates before publication to generate Web pages. Vignette CMS and Bricolage are examples of this type of system. Since pre-processing systems do not require a server to apply the templates at request time, they may also exist purely as design-time tools; Adobe Contribute is an example of this approach.

Online processing

• These systems apply templates on-demand. HTML may be generated when a user visits the page, or pulled from a cache. Hosted CMSs are provided by such SaaS developers as AspireCMS, Bravenet, UcoZ, Freewebs and Crownpeak.
• Some of the better known open source systems that produce pages on demand include Concrete5, Mambo, Joomla!, Drupal, TYPO3, Zikula and Plone, etc…
• DotNetNuke is a partially open source CMS that runs on asp.net and is free to download and install. DNN produces pages on demand but levels and types of caching can be set. There are also many additional “modules” that can be purchased or installed for free to extend the functionality of DNN as needed, many of which create data and content dynamically.
• Most Web application frameworks perform template processing in this way, but they do not necessarily incorporate content management features. Wikis, e.g. MediaWiki and TWiki generally follow an online model (with varying degrees of caching), but generally do not provide document workflow.

Hybrid Systems

• Some systems combine the offline and online approaches. Some systems write out executable code (e.g. JSP, ASP, PHP,ColdFusion,Perl pages) rather than just static HTML, so that the CMS itself does not need to be deployed on every Web server. Other hybrids, such as Blosxom, are capable of operating in either an online or offline mode.

Incoming search terms:

• inurl:Powered by w-CMS

History

dotCMS was initially developed as a Java alternative to the PHP CMSes on the market, as well as to provide a counterpoint to high cost, enterprise applications. It is the result of over 5 years of development by dotMarketing, Inc, which also developed and released the open source project management tool dotProject. In order to achieve compliance with JSR-168 portlet specification dotCMS was built upon the Liferay portal, though has since forked Liferay at version 3.2.2. dotCMS 1.0 was initially open sourced and made available in 2005 under the dotMarketing Public License. In 2006, dotCMS released version 1.2 which included the structured content engine. In 2007 dotCMS released version 1.5, which included a new user interface and permissions. In October, 2007 dotCMS 1.5 was the runner up for Packt Publishing’s “Best New Open Source CMS” award, followed in 2008 by a second place finish for Packt’s “Best Other Open Source CMS (best non PHP CMS)”. In February 2008, dotCMS users held the first annual “Open Minds” conference in Coconut Grove, Florida. Currently, dotMarketing continues to develop and improve features within dotCMS, such as the social calendar and WebDav integration.

Community

dotCMS has an active and engaged community. There is an annual users conference, a listserv, IRC channel, and Ning and Facebook groups. dotMarketing has also began work on an official community web site, which will be home to a new documentation system a la PHP.net, allowing users to comment and provide examples of code usage, as well as collaborate. The current user base includes deployments by thousands of companies, news organizations, universities, individuals, and more. More information regarding the dotCMS community can be found on the dotCMS website.

Open Minds Conference

The first annual Open Minds Conference was held February 7-10 in Miami, FL. This event was designed to bolster excitement in the community, and provide a venue for users to meet, collaborate, and network. Topics ranged from introductory installation sessions, to more advanced talks on setting up development environments, and was attended by more than 60 participants from 20 institutions. The second annual conference is scheduled for February 4-6, 2009, and will remain in Miami.

IRC Channel

For users familiar with IRC, you can visit the dotCMS channel on Freenode. If you do not have an IRC client, or are unfamiliar with their usage, dotMarketing has provided a web page based client. Either way will allow you to chat with other users and experts on the usage of dotCMS.

Technologies

dotCMS is a standards based CMS written in the JAVA programming language, and comes bundled with the Apache Tomcat Application Server. It is database agnostic and can run on PostgreSQL, MySQL, MSSQL or Oracle. It is capable of integrating with user’s authentication scheme’s, such as Active Directory or LDAP, and will support operation in a clustered or load balanced environment. It leverages a number of standards based open source projects such as:

• Apache Struts Web Framework
• Apache Lucene Search Engine
• Apache Velocity Templating Language
• Liferay Portal
• EXT Javascript Framework
• Apache Tomcat Application Server
• OSCache distributed caching system
• Hibernate Object Relational Mapping

Structured Content

The driving concept behind content stored within dotCMS is that it is addressed through a system of structures. Structures are administrated through a back end portlet where fields are assigned to them. Fields are named and given a content type and then ordered. Each structure can then be permissioned and used when creating content, and allows different types of content with consistent components to be referenced for display on the front end. A “web page content” structure could be assigned a title and body, for instance, while “events” have titles, dates, times, locations, descriptions, links, etc. Structures therefore allow the CMS to tailor itself to the content demands of the institution using it, because they can create and define structures that are specific to their needs. Those structures can then be created through relationships, allowing content from one structure to be associated content items in another. There is no limit to the number of structures one can use within dotCMS.

Other information

• Developed by  dotCMS Development Group
• Latest release  1.6.5a / 04 December 2008;
• Written in  Java
• OS  Cross-platform
• Type  Content Management System
• License  GNU General Public License v2
• Website  http://www.dotcms.org/

Incoming search terms:

• powered by joomla 1 5

Plone is released under the GNU General Public License (GPL) and is designed to be extensible. Major development is conducted periodically during special meetings called Plone Sprints. Additional functionality is added to Plone with Products, which may be distributed through the Plone website or otherwise. The Plone Foundation owns and protects all copyrights and trademarks. Plone also has legal backing from the council of the Software Freedom Law Center.

The name Plone is an homage to the Warp Records band Plone, whose music is both simple and playful. The logo represents collaboration with three dots together in a group.

MediaWiki’s “Monobook” layout is based partially on the Plone style sheets.

History

The Plone project was begun in 1999, by Alexander Limi, Alan Runyan, and Vidar Andersen. It was made as a usability layer on top of the Zope Content Management Framework. The first version was released in 2001. The project quickly grew into a community, receiving plenty of new add-on products from its users. The increase in community led to the creation of the annual Plone conference in 2003, which is still running today. In addition, “sprints” are held, where groups of developers meet to work on Plone, ranging from a couple days to a week. In March 2004, Plone 2.0 was released. This release brought more customizable features in Plone, and enhanced the add-on functions. In May 2004, the Plone Foundation was created for the development, marketing, and protection of Plone. The Foundation has ownership rights over the Plone codebase, trademarks, and domain names. Even though the foundation was set up to protect ownership rights, Plone remains open source. In March 12, 2007, Plone 3 was released. This new release brought inline editing, an upgraded visual editor, and strengthened security, among many other enhancements. Up to September 2007, there have been over 200 developers contributing to Plone’s code. Plone won two Packt Open Source CMS Awards.

Design

Plone is built on the Zope application server, which is written in Python. Plone is made such that all information stored in Plone is stored in Zope’s built-in transactional object database (ZODB). Plone comes with installers for Windows, Mac OS X, and Linux, along with other operating systems. New updates are released regularly on Plone’s website. Plone is available in over 35 languages. Its interface follows the government standard WAI-AAA and U.S. section 508, which allows people with sight disabilities to properly access and use Plone. A major part of Plone is its use of skins and themes. When working with Plone, templates can be used to customize a website’s look. These templates are written with Cascading Style Sheets. In addition, Plone comes with a user management system called Pluggable Authentication Service. Introduced in Plone 2.5, “PAS” is used to properly sort actions from different users to their respective folders or accounts. PAS is also used to search for users and groups in Plone. Most importantly, PAS covers the security involved for users, requiring authentication in order to login to Plone. This gives users an increase in both security and organization with their content. A large part of Plone’s changes have come from its community. Since Plone is open source, the members of the Plone community regularly make alterations or add-ons to Plone’s interface, and make these changes available to the rest of the community via Plone’s website.

Community

Since its release, many of Plone’s updates and add-ons have come from its community. Events called Plone “sprints” consist of members of the community coming together for a week and helping improve Plone. The Plone conference is also attended and supported by the members of the Plone community. In addition, Plone has an active IRC channel to give support to users who have questions or concerns. Up through 2007, there have been over one million downloads of Plone. Plone’s development team has also been ranked in the top 2% of the largest open source communities.

Strengths and weaknesses

Plone excels when compared to other content-management systems in standards conformance, access control, internationalization, aggregation, user-generated content, micro-applications, active user groups and value. It’s available on many different operating systems, due to its use of platform-agnostic underlying technologies such as Python and Zope. Plone’s Web-based administrative interface is optimized for standards, allowing it to work with most common web browsers, and uses additional accessibility standards to help users who have disabilities. All of Plone’s features are customizable, and free add-ons are available from the Plone website.

Plone has an excellent security record compared to other popular content management systems.

Plone’s weaknesses include Python and Zope experience requirements for those wishing to add or extend the feature set, making for a considerable learning curve for developers. Plone has been rated as lagging in repository services when compared to other major CMSs.

Features

These are some of the features available in Plone 3.0:

• Inline editing
• Working Copy support
• Link and reference integrity checking
• Automatic locking and unlocking
• Collaboration and sharing
• Versioning, history and reverting content
• Upgraded visual HTML editor
• Workflow capabilities
• Authentication back-end
• Full-text indexing of Word and PDF documents
• Collections
• Presentation mode for content
• Support for the search engine Sitemap protocol
• Support for multiple mark-up formats
• Wiki support
• Automatic previous/next navigation
• Rules engine for content
• Auto-generated tables of contents
• Portlets engine
• Support, development, hosting & training
• LiveSearch
• Multilingual content management
• Time-based publishing
• Human-readable URLs
• Powerful graphical page editor
• Navigation and updated site maps
• Resource compression
• Caching proxy integration
• Drag and drop reordering of content
• XML exports of site configurations
• Localized workflow configuration
• Adjustable templates on content
• Standard content types
• Content is automatically formatted for printing
• Standards-compliant XHTML and CSS
• Accessibility compliant
• RSS feed support
• Automatic image scaling and thumbnail generation
• Free add-on products
• Cross-platform
• Comment capabilities on any content
• Microformat support
• Installer packages for multiple platforms
• WebDAV and FTP support
• In-context editing
• Backup support
• Cut/copy/paste operations on content

Other Information

• Developed by  Alan Runyan, Alexander Limi, Vidar Andersen and the Plone Team
• Latest release  3.1.7 / #REDIRECT Template:Start date and age
• OS  Cross-platform
• Platform  Zope
• Type  Content management system
• License  GNU General Public License
• Website  http://plone.org/

Joomla is used all over the world to power Web sites of all shapes and sizes. For example:

• Corporate Web sites or portals
• Corporate intranets and extranets
• Online magazines, newspapers, and publications
• E-commerce and online reservations
• Government applications
• Small business Web sites
• Non-profit and organizational Web sites
• Community-based portals
• School and church Web sites
• Personal or family homepages

Joomla is the most popular open source CMS currently available as evidenced by a vibrant and growing community of friendly users and talented developers. Joomla’s roots go back to 2000 and, with over 200,000 community users and contributors, the future looks bright for the award-winning Joomla Project.

Other Information

• Developed by  The Joomla Core Team
• Latest release  1.5.8 / November 10, 2008
• OS  Cross-platform
• Type  Content Management System
• License  GPL

Links

• Joomla News
• Joomla Extensions
• Website  joomla.org

Incoming search terms:

• ARS Reservation System для joomla 1 5

Overall Winner

1. Drupal – Drupal is a free software package that allows an individual or a community of users to easily publish, manage and organize a wide variety of content on a website, Tens of thousands of people and organizations are using Drupal to power scores of different web sites, including
   
2. Joomla! – Joomla is an award-winning content management system (CMS), which enables you to build Web sites and powerful online applications. Many aspects, including its ease-of-use and extensibility have made Joomla the most popular Web site software available. Best of all, Joomla is an open source solution that is freely available to everyone..
3. DotNetNuke - DotNetNuke is an open source web application framework written in VB.NET for the ASP.NET framework. The application’s content management system is extensible and customizable through the use of skins and modules, and it can be used to create, deploy, and manage intranet, extranet, and web sites.

Most Promising Open Source CMS

1. SilverStripe – SilverStripe is a free and open source programming framework and content management system (CMS) for creating and maintaining websites. The CMS provides an intuitive web-based administration panel, allowing any person to maintain their website without knowledge of markup or programming languages.
2. CMS Made Simple – CMS Made Simple is an open source (GPL) package, built using PHP that provides website developers with a simple, easy to use utility to allow building small-ish (dozens to hundreds of pages), semi-static websites. Typically our tool is used for corporate websites, or the website promoting a team or organization, etc. ..
   
3. ImpressCMS
4. MiaCMS

Best PHP Open Source Content Management System

1. Drupal
2. Joomla!, CMS Made Simple

Best Other Open Source Content Management System

1. Plone
2. dotCMS
3. DotNetNuke

As expected, there are also many challenges that will affect the markets in the near future.
Web CMS to Hit US$ 2 billion by 2014

WinterGreen Research announced in its new study that web content management is poised for significant growth. Web content management markets were at US$ 372 million in 2007. The prediction is that they will reach US$ 2 billion by 2014.

Market growth is a direct result of companies leveraging the Internet as a channel and responding to the implementation of broadband networks for video and image transmission.

Web content management systems are basic infrastructure for unstructured information published to the web. Unstructured information is becoming more structured, as it is tagged with XML tags and managed in smaller components that can be re-used and repurposed.

As more companies move to purchase marketing and web 2.0 based applications based on XML and integration technologies, the web CMS market will grow accordingly.

Potential Web CMS Challenges

As we all know, web content management is a central aspect of growing the business and staying competitive. Therefore, web CMS should be of importance to corporate IT and legal departments.

Be it acquiring the very first web CMS or switching from one to another – organizations need a web CMS to do business effectively. Various national and international compliances dictate that web content needs to conform to mounting regulatory requirements and legislative pressure.

The entry of SaaS and open source CMS players changes the market by giving web 2.0 market participants strategic advantage. Managing rich media assets is an essential component of an enterprise content platform. Increasing volumes of rich media assets also means that companies are struggling to find, manipulate and repurpose rich media content across the enterprise.

DAM to Surpass US$ 1 Billion in 2013

Sparked by the continuing explosion of digital media in all its forms, such as audio, video and photos, the global market for digital asset management solutions is expected to pass the US$ 1 billion mark in 2013.

According to ABI Research analyst Zippy Aima, there are several forces driving this market to great heights, but DAM also has some significant challenges to overcome.

“Large quantities of digital media content require collaboration across all personnel and departments, from creation to delivery,” says Aima. “DAM systems’ ability to enable integration is driving demand.”

Until recently, it was nearly impossible to integrate rich media management with legacy and third-party applications and systems, such as ERP and enterprise content management (ECM) applications. Many today’s DAM solutions can do that.

Another factor motivating organizations to implement DAM is the bottom line and DAM’s ability to demonstrate a clear ROI.

Potential DAM Challenges

There are still issues to be resolved. Firstly, it’s a lingering confusion about the very definition of digital asset management and its true capabilities. It is not a subset of ECM, but a separate system, which can and should be integrated with ECM.

Other obstacles to DAM adoption include high price. According to ABI Research, the average cost of a DAM system is in the US$ 100,000 — US$ 150,000 range. User adoption and executives’ buy-in is a challenge for both web CMS and DAM.

For more research findings, check out ABI Research’s recent study ”Digital Asset Management”
Web 2.0 Future Trends

According to Forrester research, we should expect US$ 4.6 billion in web 2.0 spending by 2013, as large companies continue to embrace it.

Enterprise spending on web 2.0 technologies is expected to grow strongly over the next five years with better enterprise adoption of social networking, mashups and RSS. The market for enterprise web 2.0 tools will be defined by commoditization and eroding prices.

Potential Web 2.0 Challenges

Web 2.0 adoption may take longer than it should. Despite the major impacts the technology will have on how businesses market their products and optimize their workforces, web 2.0 will eventually be weaved into the fabric of the enterprise.

The ROI may not be very clear for many organizations, as they keep wondering whether it is possible to make money with web 2.0. This, in turn, will keep software firms guessing whether they can make money selling enterprise web 2.0 tools.

Packt Publishing

Accepting nominations since mid-July, Packt Publishing announced this week the finalists for its 2008 Open Source CMS Awards. Final voting began on Sept. 1 and runs through Oct. 20.

This is the third year for the awards, which are designed to “encourage, support, recognize, and reward” popularity and quality in open source content management systems. The finalists for each of the four main categories are as follows:

Overall Open Source CMS Award Finalists

• DotNetNuke
• Drupal
• Joomla
• Plone
• TYPOlight

Most Promising Open Source CMS Finalists

• CMS Made Simple
• ImpressCMS
• MiaCMS
• MemHT
• SilverStripe

Best PHP Open Source CMS Finalists

• CMS Made Simple
• Drupal
• eZ Publish
• Joomla
• Xoops

Best Other Open Source CMS Finalists

• dotCMS
• DotNetNuke
• mojoPortal
• Plone
• Umbraco

In addition to awards for the systems themselves, an Open Source CMS MVP Award will be given to an outstanding individual contributor. The winners in each category will be determined by a panel of four judges whose votes will be combined with those from the public. Announcements of the winners will be staggered:

Oct. 27: Open Source CMS MVP
Oct. 28: Best Other (non-PHP based) Open Source CMS
Oct. 29: Best PHP Open Source CMS
Oct. 30: Most Promising Open Source CMS
Oct. 31: Overall Open Source CMS Award

The project team for the overall winner gets a prize of $5,000, with an additional $15,000 in prizes going to winners and runners-up other categories.

To learn more about each of the projects and cast your vote, visit Packt Publishing’s finalist page.

The latest release of WordPress is version 2.6.2, released on 08 September 2008. It is distributed under the GNU General Public License version 2.

Features

• Templating system
• Integrated link management
• Search engine-friendly permalink structure
• Support for plugins
• Support for widgets
• Nested categories and multiple categories for articles
• Trackback and Pingback
• Typographic filters for proper formatting and styling of text
• Static pages
• Multiple authors
• Can store a list of users who visit your blog
• Can block site visitors by IP address
• Tag support

History

b2\cafelog, more commonly known as simply b2 or cafelog, was the precursor to WordPress. b2\cafelog was estimated to have been employed on approximately 2,000 blogs as of May 2003. It was written in PHP for use with MySQL by Michel Valdrighi, who is now a contributing developer to WordPress. Though WordPress is the official successor, another project, b2evolution, is also in active development.

WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2.

In 2004 the licensing terms for the competing Movable Type package were changed by Six Apart, and many of its users migrated to WordPress – causing a marked and continuing growth in WordPress’s popularity.

In 2007 WordPress won a Packt Open Source CMS Award.

Releases

WordPress releases are named after well-known jazz musicians. For example, WordPress 1.2 was code named Mingus (after Charles Mingus).

WordPress 1.5 was released mid-February 2005 and code named Strayhorn. It added a range of new vital features. One such is being able to manage static pages. This allows content pages to be created and managed outside the normal blog chronology and has been the first step away from being simple blog management software to becoming a full content management system. Another is the new template/theme system, which allows users to easily activate and deactivate “skins” for their sites. WordPress was also equipped with a new default template (code named Kubrick) designed by Michael Heilemann.

WordPress 2.0 was released in December 2005 and code named Duke. This version added rich editing, better administration tools, image uploading, faster posting, an improved import system, and completely overhauled the back end. WordPress 2.0 also offered various improvements to plugin developers.

On 22 January 2007, another major upgrade, WordPress 2.1, code named Ella, was released. In addition to correcting security issues, version 2.1 featured a redesigned interface and enhanced editing tools (including integrated spell check and auto save), improved content management options, and a variety of code and database optimizations.

WordPress 2.2, code named Getz, was released on 16 May 2007. Version 2.2 featured widget support for templates, updated Atom feed support, and speed optimizations. WordPress 2.2 was initially slated to have a revised taxonomy system for categories, as well as tags, but a proposed revision led to the feature being held back from release.

WordPress 2.3, code named Dexter, was released 24 September 2007. Version 2.3 features native tagging support, new taxonomy system for categories, easy notification of updates as well as other interface improvements. 2.3 also fully supports Atom 1.0 along with the publishing protocol. WordPress 2.3 also includes some much needed security fixes.

WordPress 2.5, code named Brecker, was released 29 March 2008. Developers skipped the release of version 2.4 so version 2.5 contained two releases worth of new code. WordPress 2.5 saw a complete overhaul of the administration interface and the WordPress website was also redesigned to match the new style.

WordPress 2.6, code named Tyner, was released 15 July 2008. It contains a number of new features that make WordPress a more powerful CMS: you can now track changes to every post and page and easily post from wherever you are on the web, plus there are dozens of incremental improvements to the features introduced in version 2.5.

WordPress 2.6.1 was released on 15 August 2008. It contains several bug fixes. WordPress 2.6.2 was released on 08 September 2008. It contains a handful of bug & security fixes.

Vulnerabilities

BlogSecurity currently maintains a list of WordPress vulnerabilities.

In January 2007, many high-profile Search engine optimization (SEO) blogs, as well as many low-profile commercial blogs featuring AdSense, were targeted and attacked with a WordPress exploit.

A separate vulnerability on one of the project site’s web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately.

In May 2007, a study revealed that 98% of WordPress blogs being run are exploitable.

In a June 2007 interview, Stefen Esser, the founder of the PHP Security Response Team, spoke critically of WordPress’s security track record, citing problems with the application’s architecture that make it unnecessarily difficult to write code that is secure from SQL injection vulnerabilities, as well as other problems.

Developers

WordPress development is led by Ryan Boren and Matt Mullenweg. Mullenweg and Mike Little were co-founders of the project.

The contributing developers include:

• Dougal Campbell
• Mark Jaquith
• Donncha O’Caoimh
• Andy Skelton
• Michel Valdrighi
• Peter Westwood

Though much developed by the community surrounding it, WordPress is closely associated with Automattic, where some of WordPress’s main contributing developers are employees.

WordPress is also in part developed by its community, among which are the WP testers, a group of people who volunteer time and effort to testing each release. They have early access to nightly builds, Beta versions and Release Candidates. Upgrading to these versions, they can find and report errors to a special mailing list, or the project’s Trac tool.

Sponsored themes

On 10 July 2007, following a discussion on the WordPress ideas forum and a post by Mark Ghosh in his blog Weblog Tools Collection, Matt Mullenweg announced that the official WordPress theme directory at http://themes.wordpress.net would no longer host themes containing sponsored links. Although this move was criticized by designers and users of sponsored themes, it was applauded by some WordPress users who consider such themes to be spam. The official WordPress theme directory ceased to accept any new themes, including those without sponsored links, shortly after the announcement was made. Ironically, the closure of the official site and its consequent lack of up-to-date themes drove many people into downloading themes from unofficial sites which inserted their own spam links into all themes downloaded from them.

On July 18, 2008, a new theme directory opened at http://wordpress.org/extend/themes/. It was styled along the same lines as the plug-ins directory. Any theme that is uploaded to it will be vetted, first by an automated program and then by a human.

WordPress native iPhone & iPod Touch app

On 11 July 2008, with the launch of iTunes App Store by Apple, WordPress has also released its native app for iPhone and iPod Touch WordPress app has all the features which WordPress Admin panel have. This app works for all the WordPress.com and self hosted WordPress 2.5.1 or above blogs.

Criticisms

• Several security issues but reasonable turnaround time on fixes. According to Secunia, WordPress still has 98+ security issues as of August 2008
• No built-in ‘Preview Post’ link when writing a post. A link was added to open a preview in a new window or tab, but that has caused its own confusion.
• Not great for large project with a very large amounts (hundreds or thousands) of page (rather than post) content. You could easily outgrow it if your needs grow beyond what WordPress can do. Extendable, but there are limitations. Still very good for small scale projects. Blogging is not the answer to everything for everyone. There are many advantages to making your entire website a blog, but there are some disadvantages to it as well

Latest WordPress Release

• WordPress 2.7 “Coltrane” :  December 10, 2008

Links

• WordPress News
• WordPress.com
• Download WordPress

Incoming search terms:

• carlton powered by wordpress
• internalizes powered by wordpress
• meteorites powered by wordpress