Content Management System

From UUWiki
Jump to navigation Jump to search

Main Page > Websters

Content Management Systems

A Content Management System (CMS) is a system used to organize and facilitate creation and maintenance of documents and other content (in this case for a web site). They are designed to allow many people to directly contribute to the process. Contributers sign on to authenticate and their activities are both assisted and restricted by the system. To manage this, a CMS isolates the actions and effects of content creation and maintenance from other elements (layouts, styles, menus, etc.). Both Wiki's such as this and blogging sites use Content Management Systems.
A more comprehensive description and additional details can be found at Wikipedia.

Advantages of a CMS website:

  • content can be added and maintained without "webmaster" skills
  • many people can contribute or collaborate using just their web browser
  • limits on what contributors can and can't do can be precisely defined
  • site layout, style and menus are unaffected during content editing work
  • content is unaffected during layout, style and menu modifications
  • standards and changes for layout, style and menus are applied universally
  • site mapping, indexing, site search and menu generation is automatic
  • web feed (RSS) syndication of content is usually automatic
  • media (images, audio, video, etc) presentation and management is easier to implement
  • member only features are easier to implement
  • member participation features are easier to implement
  • better for sites with many frequent changes, community and media features

Disadvantages of a CMS website:

  • can be more work to set up for a simple site
  • fine tuning the look of individual pages and elements is limited
  • CMS systems have their own menus and logic which users must understand
  • one or more people must act to administrator the site and any other users
  • requires specific software to be present or added to the web server
  • CMS software will require occasional security maintenance and updating
  • usually requires some setup and configuration of a database on the web server
  • places greater processing demands on the web server
  • backup and recovery is more complicated when a database is involved
  • poor for relatively static sites with few changes and a single maintainer

Explore the CMS world:

  • The website CMS Matrix allows you to compare features on approximately 100 different CMS solutions. The "Search the Matrix" feature allows you to filter the list according to the features that you need for your site.
  • The website Open Source CMS Systems allows you to demo 40-50 LAMP-based Portals(CMS) and review the comments left by other visitors. ("LAMP" is an acronym for 'Linux-Apache-MySql-PHP' software.)


Listed below are some CMS packages that churches use to build and maintain websites.

Plone®

Cost: FREE: (GNU General Public License)

Notes: Plone is a ready-to-run content management system that is built on the powerful and free Zope® application server. Plone provides a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. Zope is a full web application environment using its own transactional object database and programmed in the full featured, object oriented, Python scripting language.

Advantages: It is easy to create events, news items, new documents, photos, and other files. It uses both HTML and an easy to use Structured Text for those who are unfamiliar with website design. It has many add-on products that extend features available. It has a very flexible security/permissions structure which allows people and groups with different roles to have control over different aspects and different parts of the site. Plone® delivers excellent compliance with W3C web (XHTML transitional and CSS) and accessibility (WCAG and Section 508) standards. It can be set up to run on many different types of web servers (Linux, Windows, Mac, BSD etc.) A large developer community, and commercial support is available.

Disadvantages: Plone will generally require a dedicated (of virtual) web server due to its use of Zope rather than PHP and MySQL. It is resource-hungry on the server. It requires over 75 MB RAM dedicated to your site which tends to cost from $15 to $40/month. Generally it will require more learning by the webmaster. For more insights, see http://plone.org/documentation/faq/is-plone-for-me

Examples:

To try it out, create your own free site at http://www.objectis.org/ or create your own account at a Plone-based community site like http://plone.org/ For more flexible production hosting, you might look at http://zettai.net, http://interlix.com, http://quintagroup.com, or http://imeme.net.

Drupal

Cost: FREE (GNU General Public License)

Notes: Similar to Plone® but implemented using more standard PHP and MySQL resources. Originally developed for 'community' participation web sites where everyone in the community is able to contribute content. Today the program is being used for a wider range of uses, including online press (The Progressive, The Onion), academic sites, media libraries, and galleries. It can be used both for sites with very limited access (just a few authors) or by a very expansive community of users and authors with different privileges.

Advantages: Easy to create news items, single author and multi author documents, audio & video posts (podcasts), galleries (image collections), etc. The base program is highly compliant with both general W3C web design standards (XHTML strict and CSS) and accessibility standards (WCAG and Section 508 requirements). Many theme templates and lots of additional modules are freely available from the central Drupal community site. Common modules include kits which can be use to create custom content types and views. Content can be edited in WYSIWG mode or HTML using a choice of tunable editors. Regulation of user roles and privileges is very adjustable. Editing experience and viewing experience can be customized for different users. Content categorization and use of categorization is both flexible and pervasive. Technical support is available through an active user community on Drupal's community support site. A dedicated Drupal commercial hosting service option is available (Bryght Community content hosting).

Disadvantages: Many modules are not mature and many others have not been adapted to run under either the current 5.x or the previous 4.7 versions. Administration is done through same interface as is used for general site viewing (rather than a purpose specific back end interface). Strict enforcement of design and coding creates requirements that may pose difficulties for some trying to make customizations. Building a multi featured site requires the selection, installation, and maintenance of many third party modules.

Examples:

  • Follen Church Society
  • At least a couple of other UU congregations are currently in the process of launching or evaluating this CMS.
  • If you google "church drupal" you can also find quite a few churches of other denominations using it.
  • one example from the Bethlehem Lutheran Church


Mambo/Joomla

Cost: FREE (both Mambo and Joomla use the GNU General Public License)

Notes: Probably the most popular CMS. Listed together: Mambo and Joomla share a common design heritage. In mid-2005 the Miro corporation set up a "Mambo Foundation" in an attempt to exert more control via their ownership of the trademark. This was strongly resisted by the Mambo developer community, which left en-masse and are continuing their development using the name "Joomla". As these two programs continue development they are likely to become much more distinct and less able to share. Several web hosting services support use and installation through one or more of these through automated installation scripts or "one-button installs". It uses the same PHP and MySQL components as most other CMS's listed here.

Advantages: Administration is done through a separate "back end" interface to avoid limitations of the "front end" interface used during normal site viewing and navigation. Administration interface has an graphic icon driven interface that makes use less intimidating for some. Theme templates and module extensions are easily loaded remotely since the interface accepts compressed modules remotely, transfers them, and unpacks on the server before loading them for use. The popularity of the system has resulted in good availability of themes, extensions and experienced developers. Supports blogs, web feeds, multimedia, calendars, galleries, and podcasting through options and extensions. Administration interface and loose enforcement of constraints makes modification of theme templates easier than some other CMS.

Disadvantages: The current 1.0 release is in need of revision to achieve compliance with W3C (XHTML transitional and CSS) and accessibility standards (WCAG and Section 508 requirements). This release relies extensively on the use of tables in ways that are no longer recommended practice. Improvements in these areas are a major goal of the version 1.5 release. Version 1.5 will provide a major redesign and its future release date is uncertain. (Beta 1 was released October 12, 2006 and Beta 2 was being prepared for release some unscheduled date after Feb 15, 2007). Due to the large amount of base design and extensions built outside of standards, it is not clear how readily or thoroughly the design improvements will be achieved. The 1.0 administration interface has been extended such that structure is not always clear and some functions lack the visual and logical clarity of the other sections.

Examples:
Mambo:

Joomla:


Contentor

Cost: FREE

Advantages: Contentor was designed for small to medium-sized web sites, typical of sites for/by small non-profit corporations or individuals. It was developed by a fellow UU, Earl Daniels.

Disadvantages: Unclear how much usage or support there is.

Examples:


UU Template project

Cost: FREE

Notes: The term template may be a bit misleading. These file sets create a scripted (PHP) interface, a choice of two visual themes and a standard set of church web pages. It provides a user interface allowing authorized users to login to the site from any web browser. Once logged in, the authorized user can create content, perform basic maintenance, and extend the page and menu content without any web editing tools. New as of May 2006; the specs for future versions are being considered to improve it.

Advantages: The UU Web Templates are designed and prepared specifically for use by UU congregations needing to create a first web site and should allow a quick and low cost launch. The UU Web Templates can also be used as an add-on or for use in re-design of a site. The project is supported by fellow UUs so the community is limited, but shares a lot of common knowledge. There is an email list to communicate with the other users. The simplicity of the design allows the templates to function on both Linux/Unix and Windows web servers. The templates do not require the complexity of a database setup and maintenance.

Disadvantages: A limited selection of styles and color schemes are built into the design. Limitations on the degree to which a site can be extended. There is currently no support for "Web 2.0" features such as media, community/social networking and blogs. The constraints of a small community of users may create some difficulties in maintaining and growing the application. Unspecified problems have been reported.

WordPress

Cost: FREE (distributed under GNU General Public License)

Notes: Designed principally for blogs, the basic package also supports standard web pages and a multi-level menu structure. It is easily extended through a "plug-in" interface to add support for podcasting and image galleries. Recent updates allow for a site that does not contain a blog on the opening page. Because of its popularity and flexibility, it is being used for multi-purpose and some general purpose websites.

Advantages: WordPress is relatively easy to setup and understand. It is also a relatively mature and well maintained program. This has resulted in it being both very stable and web and accessibility standard compliant. The WordPress site provides extensive guidelines on how to improve and maintain accessibility. An extremely large collection of theme templates and plug-ins is available in the public domain and from custom developers. Themes are easily and quickly switched and customized from within the administrative interface. Non-blog pages and menus are relatively easy to create. The tabbed administrative interface opens on a dashboard which displays the system status and provides notices of upgrades from WordPress. Content is created and edited using an interactive WYSIWYG editor that allows tabbing between a formated presentation and direct HTML editing. The editor provides both auto-save backups during editing and spell checking. Edits can be saved to draft, or private, or published for public viewing. Its podcasting feed support exceeds those of other CMS offerings. It is common for web hosting services to supply their customers with a "one-button" installation for the WordPress application. A dedicated commercial hosting service option is available from WordPress.com.

Disadvantages: The program is designed and maintained to support the specific purpose of blogging. Congregations attempting to use it for broader purposes may encounter limitations (either immediately or in the future).

Examples:


CMS Made Simple

Cost: FREE (distributed under GNU General Public License)

Notes: To get a simple CMS site up and start managing it is relatively simple. The standard installation provides a very friendly interface, a lot of guidance, explanations of CMS concepts, and such. This makes the product easier for the inexperienced to start working with. This is a relatively new product now in stable release and getting maintenance and security updates. This CMS makes use of the preexisting SMARTY theme/template engine.

Advantages:

  • very easy to make a hierarchical website
  • very nice administration interface, ordered by role and tasks
  • standard news module, RSS feeds, file and image managers, and WYSIWYG editor
  • module manager, allowing to download and install modules from the browser
  • many modules available

Disadvantages:

  • inconsistent add-on modules (different ways of doing things)
  • lack of CMSMS functionality, a lot is borrowed from other OS software

Examples:

  • no UU users known of ...
  • other denominations have congregations using it, but this wiki still needs a showcase quality example.


Main Page > Websters

Retrieved from "https://uuism.net/uuwiki/index.php?title=Content_Management_System&oldid=7382"