When choosing the best content management system for your project, it is important to weigh both the technical and non-technical pros and cons. Both technical and non-technical reasons can ultimately affect the bottom line cost. Therefore, it is not recommended to simply choose a content management system based solely on technical language or feature set. In this article, we will take a look at an open source content management system called Radiant CMS.

Radiant is a Ruby on Rails based solution that works with a variety of databases. It has a few years of development and a couple noteworthy deployments. There are technical and non-technical reasons why Radiant CMS is a good choice for a content management system.

Technical Reasons to Choose Radiant CMS: It's Ruby on Rails based which can speed development by taking advantage of the convention over configuration paradigm. In addition, the Radiant code base has excellent automated coverage in unit tests. This means the code is well tested and robust. Unit test code coverage can be one aspect to measure when considering open source content management systems. In fact, we could suggest the amount of code covered by automated unit and integration tests should be considered when choosing any open source library and/or framework. It is an easy indicator to measure and compare. But, that is an entirely different conversation.

Radiant CMS also has an excellent extension system. This allows customizations required by your project to be made. When choosing a content management system, the ability to add and maintain any customizations should be an important factor. This point should be considered not only from the beginning, but how your customizations will evolve as upgrades and enhancements occur within your chosen content management system. In other words, if the core CMS is modified to provide the custom functionality, how can upgrades or patches from the core CMS developers be applied to your modified version. Radiant's extension system provides this separation of concern.

The Radius tagging system of Radiant is fantastic for adding dynamic functionality. It is nice that tags can be added directly to page content rather than some kind of comment or special character sequence in order to indicate non-static content.

Non-Technical Reasons to Choose Radiant CMS: Radiant has an elegant, intuitive administrative interface. It is not intimidating to the non-technical user. In fact, the design encourages people to embrace using the system, because they assume it is going to be easy to pick up and learn.

The lack of workflow functionality can be considered a feature in many cases. In competing CMS products, workflow can seem like an attractive feature at first, but is often hindrance to configure and work around for projects which require only a few administrators of content.

An additional, non-technical reason to choose Radiant CMS is cost. The project is open source and the community of ruby on rails developers and ruby on rails hosting providers is growing, so your cost risk of obtaining these resources is minimized.

Conclusion

From a technical perspective, the open source, Ruby on Rails based Radiant CMS makes an excellent choice. From a non-technical perspective, Radiant CMS makes an excellent choice as well. When combining both perspectives, we have had many positive project experiences and deployments using Radiant over the past year and a half.

Whether you prefer developing in ASP, PHP or Colfusion, Adobe Dreamweaver and the WebAssist Super Suite extensions can turn an ordinary website into a dynamic database-driven workhorse that rivals those from professional developers costing tens of thousands of dollars.

Super Suite extensions for Dreamweaver

Just like a professional carpenter, the right set of tools can make all the difference in the finished product. In Dreamweaver, having the right set of extensions can not only allow you to build more extensive, usable websites, but they can also save you an immense amount of development time and frustration.

WebAssist Super Suite gives you The Power to Build Anything

The Super Suite extension package covers everything from website security, user administration, user login, site cookies, sessions, database administration, email processing, dynamic dropdowns, a full ecommerce shopping cart, a website import tool, Eric Meyer's CSS Sculptor, a full-featured text editor, dynamic Flash charts, dynamic Google map integration and a whole lot more!

Database-driven websites, e-commerce and more

The Super Suite set of extensions gives Dreamweaver users the tools to create every facet of a functional content management system, full featured forums with access-level rights, complete website database administration tools including search, add, edit, update and delete fuctions, full digital file upload and download features, and a complete ecommerce shopping cart system with fully customizable storefronts. All this is achieved through an extremely easy-to-use wizard interface which walks you through each step in simple, intuitive fashion.

Easy-to-use Dreamweaver wizard interface

Super Suite can be easily integrated into your current site Dreamweaver template. The wizards take you through the steps needed to configure your options, you choose your template, and Super Suite creates all necessary pages, navigation, recordsets, CSS and javascript. You simply upload the new pages and files to your server, and the new functionality is live, with the look and feel of your existing website.

Create advanced Dreamweaver websites without knowing any code

WebAssist Super Suite extensions are perfect for Dreamweaver users who are hesitant to dig into the code. The extensions create all the code for you, and you can easily return to the wizard at any time to make changes. Super Suite has some similar functions to Adobe Dreamweaver Developer Toolbox, but it includes one-of-a-kind extensions like the iRite WYSIWYG editor for integrating FCKeditor into your Dreamweaver websites, CSS Sculptor which allows you to create complete standards compliant websites in one easy operation, and Site Import which allows you to import complete websites including all HTML, CSS, script, Flash and image files onto your local drive.

Advice from a Super Suite user

As a Super Suite user, I have used all their extensions extensively in my client websites. The ease-of-use and the Dreamweaver integration make them a must-have extension bundle if you want to develop websites faster, create more intuitive and complex websites, and make more money as a website designer or developer.

Adobe Dreamweaver Compatibility

The WebAssist Super Suite package is an all-inclusive Dreamweaver toolkit which provides developers with all the necessary tools to make dynamic database-driven websites in Adobe Dreamweaver. The extensions are compatible with Dreamweaver 8 and Dreamweaver CS3 on both PC and Mac. PHP, ASP and ColdFusion are supported by all the extensions.

Introduction

Semantic web as defined by the creator of the web Tim Berners-Lee is "a web of data, in some ways like a global database" (Berners-Lee, 1998). To elaborate further Mr. Berners-Lee explains in an interview held by IDG Now, data is expressed on computers as associated files with applications that deal specifically with information, an example would be, data in calendars, bank systems, spreadsheets, and database application. Looking at a web page, data is not clearly defined and not associated with any of the applications usually on computers. Semantic web will allow data to interact and connect together; it will bring on a common data format for all applications, for databases and web pages alike (Moon, 1999). Semantic web is not to build an artificial intelligence system which allows computers to understand what humans write on web pages; on the contrary, it is an attempt to make web pages more understandable and well-defined to support automatic extraction of data from within web content (Berners-Lee, 1998).

Analysis

The emergence of the web and the way HTML took off was driven by how society's needed to grew, from Internet chat to file transfer to high-end communities through blogs and wiki's. HTML was not limited to web content, knowledge base and help files adapted the language as a format to document software applications and provide training material. The revolution of technologies on the Internet allowed companies like Google to index pages; a thought that was very far away, says Tim Berners-Lee in his lecture at MIT. Web services have evolved to pave the road for distributed information and modular programming allowing interoperability among sites. Through XML, data in one site can be used by another using the common protocols and standards supported by both (Berners-Lee, 1998). XML defines schemas that deal with fields of data, what is required is a system that can tell the computer what sort of information (data) it can derive from within a page (Moon, 1999). With Web 3.0 a site will provide data that can be navigated through and extracted from multiple sites, this is a result of the fact that semantic web data model is closely related to a relational database where records of data share common fields that connect them together (Berners-Lee, 1998).

The solution provided to support semantic web is in the form of metadata that describes the data contained on web pages. Resource Description Framework (RDF) is a base to manage metadata; it is the ground that computers can use to exchange and interact with applications on the Web (W3C RFC, 1999). The applications for RDF include digital libraries, online catalogs, and indexing systems that are usually associated with content and content relationships models deployed in most web pages. With RDF data within business portals will be analyzed and identified as resources, properties, or statements transparent to the domain, further more, the specifications will merge with other documents to comprise a framework of classes. Classes organized as a hierarchy comprises a schema that can be reusable as metadata definitions along side multiple platforms. Resources created in this hierarchy can be identified using a resource identifier (URI), which enables a document given to a machine with this identification to be recognized by the system and triggers it to dig and find similar data (Berners-Lee, 1998).

Implications

Semantic web can be the solution to overpower the limitations of current information management systems in finding and extracting data from unorganized resources. RDF is meant to describe any data regardless of its character, location, source, or type, the concept of URI is richer to uniquely identify any object on the web (Berners-Lee, 1998). The pillars of Semantic web are standards and common protocols that are the bases for knowledge representation; HTML, RDF, the data language resource description web ontology language (OWL) that describes to the machine what is going on, in addition to RDF1 which is a query language to make inquiries among machines much easer, will all emerge and collaborate to bring in more to the web and more intelligent programs that will bring the Internet more closer (Cleave, 2004).

The current research and implementation of Abilene network and the Next Generation Internet (NGI) Internet 2 of high-performance backbone network linking major universities and research labs across the US, is a good foundation for what Semantic web can do, and represent the perfect platform for grid computing, digital libraries, virtual laboratories, and distance learning (Abilene, Internet2). Internet2 or I2 was developed by a group of universities in 1996 providing improved connectivity standards to reach 10gbps (gigabits per second). With more than 227 universities and libraries connected, network based applications and experimental programs can run on this network of high-bandwidth connection feeding on the latest technology of gigabit Ethernet and IP protocol version 6 (Reardon, 2004). Semantic web standards can be the base of material and data distributed on this network, providing the best test platform to explore the full potential and what can be achieved.

Conclusion

Tim Berners-Lee believes that with Web 3.0 we can succeed and fantastic things can happen, but the infrastructure need to be built, laws of privacy and security need to be revised and honored, further more, the web need to remain open for researchers to allow for continuous upgrade and development. Semantic web will kick off when individuals materialize the need to work on data processing, and think about collaborating their data, with company's information and that of the government (Moon, 1999).

References:

1. Berners-Lee, Tim. 1998. Semantic Web Road map.W3C team. (14 October 1998) http://www.w3.org/ DesignIssues/Semantic (accessed 16 Jul 2007)
2. Moon, Peter. 1999. The future of the Web as seen by its creator. IT World IDG Now (7 July 1999) http://www.itworld.com/Tech/4535/070709future/ (accessed 14 Jul 2007)
3. W3C RFC. 1999. Resource Description Framework (RDF) Model and Syntax Specification. W3 Consortium (5 January 1999) http:// www.w3.org/TR/PR-rdf-syntax/ (accessed 20 Jul 2007)
4. Cleave, Kenith Van. 2004. Regis University Database Practicum Experience. Regis University. (14 November 2004) http:// trackit.arn.regis.edu/dba/Thesis%2520Papers/

   kvancleave_2004Bfinalreport_20041118.pdf (accessed 16 Jul 2007)

5. Abilene, Internet2. http://abilene.internet2.edu/about/ (accessed 17 Jul 2007)
6. Reardon, Marguerite. 2004. Internet2: 2004 and beyond. CNET, News (24 August 2004) http:// news.com.com/2100-1034_3-5321053.html (accessed 19 Jul 2007)