Working at ITD, I had the opportunity to redesign the North Dakota Highway Patrol's website. This was both a redesign, and a Drupal conversion project. Using Drupal allowed us to develop a very nice looking site that can easily be maintained. Content can be maintained by the people who are familiarwith the organization, the staff of the NDHP. www.nd.gov/ndhp is built in Drupal using Zen.

Riven Design has converted the Central Dakota Humane Society's website to Drupal.

The new CDHS site features a pet resource library, galleries of available pets, a news section, and much more.  Several custom content types, and extensive use of the Views module allowed us to make the nice looking and easy to maintain. Content is placed in appropriate menus automatically when saved, and the library and pet galleries are created dynamically. This site's theme was developed with subtheme method, using Zen.

The changes on this site weren't entirely for the sake of change. I've wanted to change to Drupal for a while, but I just didn't want to spend the time. WordPress was working fine and I had no real reason to change. Now I do. I've been building some other sites for family and family businesses using my personal hosting account. These sites have for one reason or another all changed to Drupal in recent months. One of Drupal's advantages is the ability to build multiple sites on the same code base. A multi-site installation. Other platforms have some form of this ability too, it's not unique to Drupal. In my case though, it was a very helpful ability. The only thing keeping me from using it, was this site. Due to my hosting structure, this site's directory was the most obvious location for an installation like this. Now that I've switched this site over, the rest of them will be moving over to share the code base shortly. As each one moves, that's one less code base I need to keep up-to-date. I have a little variability in the modules the various site's use, but it should still give me a 60% or more reduction in labor for Drupal updates. Same sites, same code, same function, 60% less work to maintain. I may be busy, but I just couldn't afford not to take advantage of a time saver like that.

After a lot of thought, I've switched this site over to Drupal. I really like WordPress, and I plan to continue designing for it, but for my purposes Drupal will be a better fit. While I could have matched the new site structure to the old one, I decided to restructure. My old site map had become a little conveluted and I took this opportunity to straighten it out. I'm using PathRedirect to ease the transition, and PathAuto make the new sitemap easier the maintain.

For  those who might be interested, here's a few more details of revised site:

• This site theme is built on the Zen theme using sub-themes.
• I'm using Mollom for spam control
• I've continued to use Google Analytics
• I've used a dev version of LinkToContent to make in-site linking easier.

I'm in the process of making some signficant changes to this site, and I seem to have crossed feeds with another site. Hopefully this post will straighten things out. The transtion to Drupal from WordPress is underway.

You have your site setup properly, a beautiful design, perfect content... that's everything right? Do you have RSS feeds? Can people subscribe to your site? Quick, off the top of your head, what's your site's feed called? Do you know? What's the feeds URL? Is it available from any page in the site, or just the home page? Do you have multiple feeds? If so, where are they available from? Here are a few things you can do to make it easier for your users to subscribe to your site.

• Make sure your RSS feeds have easily identifiable names. This is configurable in a lot of content management systems (CMS).  "News" might make sense to you, but when your subscriber has multiple feeds they won't know who's "news" is whose. For a single feed I would suggest the site name. For multiple feed sites, I'd suggest the site name and an individual identifier like "site name - news" or "site name - blog".
• Make sure your feeds are easily available. If a site has a feed, but it can't be found, it's not benefiting you. It might makes sense to make the news feed accessible from the news page, and the blog feed from the blog. That's a reasonable organization. You might however, want to also make them all available from one unified location. I'd suggest the home page,  or a dedicated subscriptions page if you have a number of feeds available.
• Do your feeds work? Subscribe to all of your feeds, and check them regularly. Make sure that they work, and they display your content as expected. A surprising number of RSS feeds I see don't display properly, or have errors that don't allow them to be viewed at all.

Don't overlook the details of your site. It can be a little thing like a malfunctioning or poorly named RSS feed that keeps your from that one important contact you needed.

My most recent project at Riven Design was a brand new Drupal site for Whitecap Custom Rods. The owners of WhitecapRods.com pride themselves on building rods "with an enthusiasm for excellence". It shows in their work, and I hope it shows in their site.

My business site, RivenDesign.com, has a new look. As well as the new style, I've improved the accessibility with better skip links and a better use of headings. It also has an updated version of Drupal.

I just noticed at Dries Buytaert's site that New York State Senate is using Drupal. It's now a very stylish looking Drupal site. Its' visual style is quite nice, but what lurks below the surface?

• No skip links to bypass blocks of content for screen readers or keyboard-only users
• Links not clearly identified
• No hover or focus effects on links to assist in navigation and link identification
• No level one header (h1) on home page to identify the page
• Drop down navigation is useless for keyboard-only navigation. It leaves some content extremely difficult to reach, if not completely beyond reach.

Why the half measures? Making a site accessible is more work. Making a site this un-accessible takes an active effort. The default CSS property for a link is to have an outline. This site has a focus outline property of zero. It's turned off so that a link with focus is not visible. An active effort to remove one property that identified focus, without adding another in its place. The default link property has an underline text-decoration. This site uses links with no text-decoration. A property helpful for identifying links was actively removed without replacement. I'm happy to see a very good platform like Drupal being more widely used, and this site is a good place for it. Dynamic content, multiple RSS feeds, press releases and more. All features with which Drupal excels. Unfortunately this is a bad example of Drupal theming. A good layout, a good overall design, but no thought to accessibility. What could have been a beautiful site, unfinished.

I was recently given the opportunity to review the Packt Publishing book Drupal 6 -  Social Networking by Michael Peacock.  I'm impressed. The book was well written and well organized. It starts with the basics of a Drupal installation, and quickly walks you through to the more complex configuration of a Drupal site with a social networking focus. While you might not be starting a new social media website, there are aspects of social media that can benefit almost any site. Blogs can drive traffic, and forums can aid with project discussions. Do you have a FAQ section on your site, maybe a well done WIKI would be a better choice. The possibilities for enhancing an existing site are huge. Like all good technical books, this one made me think. Michael Peacock made me reevaluate what a website is, and what it should be. I'm not yet planning a dedicated social media site, but I'm giving serious thought to how I can use social media function to improve my current projects.  If you're a designer or developer using Drupal, then you need to read Drupal 6 -  Social Networking.