Evolt.org is delighted to announce that it has moved its main site from a bespoke solution to Drupal. When we first launched evolt.org, content management systems cost USD $100.000 and more, so we took the revolutionary step of building our own (and later open sourcing it). For the last 6 years, evolt.org had lived on a custom built CMS, migrating from MS Access and Windows NT, to Oracle and Linux to MSSQL and Windows 2000 along the way. The previous evolution was launched in December 2000 (yes, really), and had served evolt.org extremely well.

However, over the last couple of years, we've increasingly wanted a few things that our previous system couldn't do without much more developer time than we had available, particularly:

  • Support for Internationalisation (i18n) and Localisation (l10n)
  • A new front end, based on CSS layout

and it occurred to us that we'd be better off standing on the shoulders of non-evolters in producing new functionality, so we didn't always have to code everything ourselves from scratch. We also felt a desire to use free tools that were within the reach of every evolter, rather than the (no less capable) proprietory (and pricey) software we'd previously used.

The solution was obvious: move from our home-grown CMS to a packaged Open Source one. A number of evolters had had good experiences with Drupal, so that's what we chose, running on Debian.

Now we're running on Drupal, we benefit from security updates, fixes and new functionality, leaving us to concentrate on evolt-specific bits. Finding time to work on the evolt site is often hard for our all-volunteer workforce, so this is obviously tremendously helpful, and as evolt.org is all about exchanging skills and experiences with our fellow web developers, this very much feels right, as well as useful.

Our solution

We've created a customised install (rather than just a simple template edit), to faithfully recreate the design and HTML mockups created a long time before Drupal was chosen. We have installed a small number of modules for the launch functionality, but expect to be adding more over time.

We'd also very much like to be able to contribute improvements back upstream, whether that be code, or simply suggestions on making Drupal even better.

Getting to Yes

To build consensus for the Drupal solution among the wider evolt community, we built 2 temporary sites as proof of concept demonstrators:

  1. Minimal functionality mockup of an evolt theme
    This challenged the stereotype of Drupal sites are Bluemarine (although similar accusations can be aimed at most CMSs, usually equally invalidly), and showed that we could make the site look the way we wanted. It also started people visualising how the site could be, and therefore making the mental jump to the future state.
  2. Full Drupal install with basic theme
    This enabled members (particularly those with admin rights) to understand how the non-public face works and have a play with it, engaging them in the potential functionality. We installed a few fun sample modules to start building enthusiasm for not having to code generic stuff for ourselves.

While a few members did get stuck in the mentality of It won't be exactly like the current site on launch day, most people got it quite quickly. While we did get bogged down by our (all volunteer) developer community having Real Life™ get in the way, we finally launched it at the weekend, to general approval.

Comments

boris mann’s picture

Martin, big congratulations to you and the entire evolt team for bringing this live. I just logged into my account again and see that I've actually been around for almost 4 years (proud user #29818)....right about the time I started taking an interest in Drupal.

This showcase announcement in the forum is great, but we would love it if you extended it with some more detail for the case study section of the handbook.

Also, I notice you are using the "propstar" module. That module isn't actually even in CVS here. Have you done modifications to it? Will you commit it? How does it compare/contrast with the nodevote or voting modules?

Again, looking forward to drawing more evolters into the mix here on Drupal.org.

dries’s picture

I'm user #16547! I even made a comment on http://evolt.org/node/15665 back in December 2001. Thanks to Drupal's tracker features I was able to find my 4 year old comment in less than 5 clicks. How cool is that? ;)

Steven’s picture

http://evolt.org/search/node/dries

The benefits of rare first names ;).

--
If you have a problem, please search before posting a question.

philipk’s picture

Hey

Another big site has just started using Drupal, they haven't mentioned it though : (

http://www.theonion.com

ArunK’s picture

It would be really nice if the default installation could work straight out of the box to make something like TheOnion.com.

sepeck’s picture

question, what do you think it is that the onion does different? Any site that you intend to 'own' needs some custimization as there is no one size fits all. Especially if you are going to build your own look and field. A news site is different from a blog site, a news feed site is different from a local school reunion site.

I can't see things from your perspecitve so, what is it that you see the Onion doing that you want to do and can't? Perhaps someone can give you some pointers.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mount

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

kbahey’s picture

I think he is referring to the multiple regions and columns on the site, as opposed to Drupal's current 2 sidebar + center content layout.

In any case, the ability to add blocks anywhere will be in Drupal 4.7. It will still require themes to be changed to do that though, but the ability will be in the core API.

--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

sepeck’s picture

I understand that, but I am not willing to guess as to what aspect he is refering to and would like to hear what he thinks is missing.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mount

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

ArunK’s picture

I mean being able to install Drupal and putting up the basic structure of the site fairly quickly, a news/blog site with a forum. The default installation is OK, its pretty easy to do. The level of customization they have done on that site is very extensive, I guess I'm looking at it from a non programmers point of view.

eldarin’s picture

Looking at theonion.com XHTML source it doesn't seem immediately recognizable as a plain theme-evolved first page. They even use sIFR for Flash-headings ...

A guess could be that they are quite PHP-savvy, and use PHPtemplate for extensive customization. They can also make a page with PHP-formatting - but then it would show more clearly what engine they used, I think.

An indication of the extent they have their own PHP stuff, is the advanced-search page (link only available via article pages).

The same goes for evolt.org - as they stated, and seems an indicator they know their stuff too. That's only natural for big, professional sites. They either have the competence inhouse, or hire their guns.

If you're a small fish with little computer-savvy you can run Drupal with diapers, but it's not always as good-looking, of course. If Drupal provides one really good-looking theme, then everyone would use that one. Then those who'd like to change the theme structure would still be getting into the same PHP rut.

Drupal is not a (X)HTML builder, like MS FrontPage, DreamWeaver etc. , but perhaps support for these could be better - to fend off many of the newbie obstacles. Unfortunately, theme engines like PHPtemplate might not be so useful in this case. Anyways, getting into the logic of what blocks to display when or where is a balance between a gazillion options via the (admin)user-interface or having a lighter system with a clean PHP API for logic control (like now).

Imagine the support nightmare, if Drupal had settings/options for where blocks could be placed, or when, for most URLs, users, taxonomy etc. ...
Developers would do nothing but answer "how do I"-questions about fiddling with site-design issues.
:-)

jeforma’s picture

Even though it isn't as customized as those two sites are but GameBGS.com is a one-in all game community. We have over 75 members and more then 2300 nodes ;)

We are growing very fast and all this is with the help of Drupal.

Just hope they make the image module alot more sophisticated in the Drupal 4.7 upgrade. This is what my whole site is using, but when i see other sites like those two using Drupal, I am really amazed at the work, never thought Drupal could do something like that. I would like so much to be able to customize my website like that but unfortunaetly the PHP skills are missing me...

We can always hope that Drupal will offer an easy way to arrange stuff in the next version ;)

www.gamebgs.com