Installation went fast for both Windows and Linux, and you can run Alfresco with JBoss Portal 2.2 or Apache Tomcat. For most of my testing I used Windows Server 2003 and Tomcat. The main Alfresco work area continues to be well organized, with breadcrumbs to jump around quickly and summary areas that show available actions. Additionally, each user can create custom views to their documents and tasks. On top of this, Alfresco 2.1's portlet container enables users to access their spaces, tasks, documents, and Web Forms from JSR-168-compliant portals.

Click for larger view.

After creating user accounts and shared spaces (which can be further broken down by language), I started my Web Content Management (WCM) tests by using Adobe Dreamweaver CS3 to design Web pages and style sheets. Further, the CIFS (Common Internet File System) feature let me drag and drop these assets, existing Web pages, and rich media into the repository. I liked the new Web 2.0 user interface that let me conveniently zoom into a folder or content in any space – then preview Microsoft Office files, images, and video.

You may not need to do a lot of development because there's a nice library of sample forms for entering content (articles, news flashes, and multimedia) and site components (navigation, recent items, RSS feeds, site maps, and mashups) that add functionality to pages. I also published Alfresco content to WordPress and TypePad blogs.

Administration, a traditional Alfresco strength, is now even better. Using wizards, I quickly built a library of custom SmartWebForms. These enabled content contributions to enter and submit material in the correct format. Editorial workflows (created the same way) kept reviewers informed, using e-mail notification, of pages they needed to approve. As before, Alfresco includes extensive rules that automate both routine and complex tasks. For example, in a few steps I created a rule to watch a space for newly approved documents and convert them into PDF files.

Other changes in Version 2.1 let me check for broken links, set a time when content is to be published, and expire content.

The previous version enhanced content deployment in some important ways. For example, I published a Web site to multiple servers. For even more efficiency, Alfresco's transactional deployment function pushed recent content updates (rather than publishing a whole folder or site section). Additionally, the software now tracks these individual changes and there's immediate rollback to prior versions of a site.

Effortless document capture
Underlying WCM is Alfresco Document Management, which I accessed from the common work area. Users can also interact with documents from other interfaces they may already know, including shared drives, portals, WebDAV, and FTP.

A smart folder structure similar to what you'd find when working with Web content holds documents – which enabled me to create rules to reduce manual processing. For instance, after users responded to an "approve/reject" e-mail, Alfresco moved the draft document to the appropriate folder and performed any additional steps.

I liked the way Alfresco automatically extracted metadata from documents and then categorized them. Afterward, the Google-like OpenSearch (available from Internet Explorer 7 or Firefox) helps users find material quickly in the repository.