Member for
12 years 5 monthsPartner at water&stone, ex-ComputerWorld columnist and author of the Joomla! Bible, the Drupal Themes series and the Drupal 7 Bible.
Partner at water&stone, ex-ComputerWorld columnist and author of the Joomla! Bible, the Drupal Themes series and the Drupal 7 Bible.
In February of this year, Phase2 Technology acquired control of the popular Drupal-based Open Atrium system from its creator, Development Seed. Open Atrium is a team collaboration solution built on the Drupal CMS. Open Atrium is often used in team situations, including intranets and project management environments. The system comes with a blog, a wiki, a calendar, a to do list, a shoutbox, and a dashboard to manage it all.
We tracked down the Phase2 Technology team to ask them about their plans for Open Atrium. CEO Jeff Walpole and Product Manager Karen Borchert were kind enough to take the time to answer our questions.
Phase2 is very excited to be involved with Open Atrium, but we did not want to move too quickly to change something so many people use and love without first serving the community and providing maintenance to its underlying module stack. Earlier this year, we released support packages around Atrium that allow more users the ability to implement and use Atrium with the help of our team's services. In the months since taking over Atrium, we've been delving more deeply into the involved and vibrant Atrium community to try to understand best what users are looking for in this product. We've talked to users about everything from technical needs to theming to documentation to community involvement. We've built some training around Atrium that we've conducted with some clients, and we're currently preparing a stable 1.0 release (it is officially still in "Beta" status). One thing that is certain is that we are looking to this community to be part of that road map and part of the growth of the product. We want to start by giving the community a more public place to see and find contributed Features that they might use for their own Atrium instances. And then we want to see more community involvement in building and improving Atrium in the future.
Editor's Note: The following aritlce is authored by Ric Shreves and first appeared online at Open Source CMS Pro. Permission has been granted to repost the article here at CMSReport.com.
Now that Drupal 7 has gone through a couple of Release Candidates, we feel confident that what we can see on the screen today represents very closely what everyone can expect in the final Drupal 7 production release. So, with some certainty at our backs and the release date just around the corner (we hope!), we thought it was time for us to present a Drupal 7 “first look,” that is, an overview of what everyone can expect from the new Drupal 7.
There are literally hundreds of changes in Drupal 7. Many of those changes are “minor” in the eyes of most users, indeed, they are essentially invisible. This doesn’t mean those small changes aren’t important, simply that they aren’t on the radar for the average user. In this article we are going to focus on just the highlights, in three key areas:
The first thing you notice when you fire up Drupal 7 is a new look and feel. For the first time in years, the release includes new themes. The only holdover from previous releases is the Garland theme, which has been updated to be Drupal 7 compatible. The new themes include:
Of the four themes (three new ones + Garland), only Garland and Bartik are ready to use on the front end of the site. Stark is purely a base theme, barren of all styling excepting only the default system styles. Garland remains, well, Garland; it's basic and offers not a lot. Bartik is a big improvement with more than a dozen regions (module positions) available. Still, visually, Garland and Bartik are not worlds apart. Some additional variety would have been nice. (We note that the theme Corolla, which was included in earlier Drupal 7 beta releases did not make the final cut, sadly.)
The inclusion of a base theme (Stark) is a nice move -- giving themers who don't want to use Zen (or other external starter themes) an easy way to build their own themes via sub-theme creation. One of the most welcome changes in Drupal 7 is the revision of the administration interface. This is not a minor tweak – this is a complete revision of both the interface and the information architecture. Long overdue, I think we all can agree…
The new admin interface includes not only its own dedicated theme (Seven), but also a new overlay, toolbar and shortcuts menu, as shown in the screenshot, at right. The overlay gives you a light box approach to the admin layer, preserving in the background the front-end theme. Having a dedicated theme for the admin system is a huge improvement in usability for the system and that alone would be reason to celebrate, but changes don’t stop there.
The new toolbar is anchored to the top of the browser window, reminiscent of the popular Admin Menu module many of us used in the past. There is also a configurable shortcuts menu present on the bottom edge of the toolbar; you can add your own favorites to the shortcut menu. A related improvement in look and feel is the inclusion of the Vertical Tabs functionality in the core. The functionality improves usability and reduces admin system clutter.
The Drupal team has also taken a fresh look at the admin system’s labels and information architecture. They’ve cleaned things up, eliminated redundancies and clarified labels. All in all, the admin system changes finally bring Drupal into a state of usability that will make the system much more accessible for many non-technical users.
The final area I want to highlight is a set of minor changes that will be meaningful to old Drupal users. Drupal 7 has “cleaned house” and done away from some of the legacy features that, frankly, weren’t of much utility. Gone in Drupal 7 are the Mission Statement functionality and the Footer Message. The site Search is now simply a block, instead of having two different versions of the same functionality. Also gone is the Theme Switcher option for users. Again, changes that clean things up, reduce complexity, and improve usability of the system as a whole.