IBM så på blandt andet Typo3 og Mambo til et større projekt. De valgte Drupal.
Drupal is a relative youngster compared to other content management systems (CMSs). However, we got the impression the framework was well written, robust, very extensible, and seemed to have a thriving development community that was generating a lot of adoption and support.As with other CMSs, the framework was very extensible. Many of the features we needed were provided as modules that could easily be snapped into the core functions of our Web site.
The framework and templating (theming) system are all written in PHP; there is no separate tag language to be learned. If you need to break out of the framework, it is very easy to do. (Of course, this isn't recommended, but it does offer ultimate flexibility.)
Session management is built into the core functions, which was more than other CMSs provided. This could help us pass some hurdles later on.
Drupal is known for scalability, or ease of growing a Web site from a small set of users to an enterprise level. The framework also has the ability to 'throttle' areas of the site that could cause potential problems during heavy traffic situations.
There is still an apparent learning curve to the "Drupal Way" of creating sites, but significantly less compared with other CMSs. The ability to use PHP to move freely between the business logic layer and the presentation layer (using the PHP template engine) was also very appealing.
Længere artikel med grafer fra IBM
Yahoo! skulle samle deres designeres viden på et centralt netsted, så den var tilgængelig og - ikke mindst - brugbar for alle.
Some things we thought about when choosing our CMS:
- How easy is it to update content?
- Does it support collaboration? Can it generate diffs or do rollbacks?
- How extensive are the classification tools? How many vocabularies are supported? Does it support parent/child relationships?
- How does it handle rights? Can we set different rights for contributors, editors, and administrators?
- How easy is it to customize and extend?
Ultimately, we chose Drupal because of its breadth of capabilities, powerful taxonomy, and extensibility.
Greenpeace UK er meget åbne om deres evaluering. De lister deres vigtigste 35 krav i et regneark og kalder forskellige firmaer/CMS-integratorer til hus for at fortælle. De ender med Drupal. Skalérbarhed, fornuftig databaseløsning, nyhedsaggregering er nogle af de features, der vinder Greenpeace og deres konsulentvirksomhed over.
It's been an extremely tough decision to make because there are very real advantages (and disadvantages) to each of the products we've considered. And all the people we've interacted with throughout the process we've followed have been so friendly and helpful and passionate which makes even announcing this difficult, but in the end, given our specific requirements and situation, we've decided that Drupal makes the most sense.
Se regnearket med fordele og ulemper
Telecentre.org fik Drupal ud fra følgende overvejelser:
Most importantly, Drupal was alone among all CMS options in its compatibility with a distributed network approach. The platform is essentially built for exactly this kind of approach: it supports ubiquitous outbound RSS feeds, complex aggregation of inbound feeds, per-feed or per-item non-exclusive tagging, and native support for blogging. Compared to the other options, which are virtually all CMS platforms that have developed distributed community features, Drupal is innately oriented towards community networking and distributed content creation.
Læs mere om Telecentre.org og Drupal
CopenHagen Business School valgte Drupal til sine blogs Not a green Dragon (Asian studies) og Cultonomics (Business, Language and Culture). Drupal sørger her for at hvert indlæg kan få relevante emneord og gør det tillige let at uploade og indlejre videoer.
De fortæller ikke offentligt hvorfor. Men kilder tæt på Drupal.dk siger, at de er hjertens tilfredse.
Gallery valgte Drupal fordi de så, at det fungere for andre store sider. Og fordi de havde adgang til nogle Drupal-udviklere.
When it came time to choose a new CMS, we wanted to make sure that we chose one that scale to handle our needs, was under active development, had a large and active community and was easy to customize. We wanted to make sure that if we did have to make changes, they could be mostly localized into the theme code so that we could avoid tweaking the framework code and winding up with another forked CMS.
Gallery om vejen fra gammelt CMS til Drupal
Information valgte Drupal pga. økonomien og udviklingsmulighederne:
Informations gamle side var baseret på et ’frygteligt hjemmebrygget system’, og den fejl ønskede han ikke at gøre igen.
Derfor tog han for godt to år siden kontakt til et par amerikanke aviser, der allerede var i gang med at udvikle deres netaviser i Drupal og spurgte, om ikke de skulle formalisere et samarbejde.
Siden har flere store aviser skiftet over til samme platform, heriblandt The New York Observer og Die Welt, og efterhånden tæller det internationale samarbejde – theopensourcenewspaper.org – 30 internetmedier.