Posted by dries on September 4, 2006 at 6:29am
We need a Drupal leaflet/flyer/one-pager to hand out at conferences, and most notably at Euro OSCON in 3 weeks (deadline).
Let's see if this group is in the performing stage, or whether it is stuck in the forming, norming or storming phase?
Comments
First post!
The old brochure is here: http://cvs.drupal.org/viewcvs/drupal/contributions/docs/marketing/bookle... (killes pointed me to it in our DrupalCon group discussion).
It is very old at this point, and yes, we may have some extra copies still kicking around, but we just need a simple "one pager" with basic details which can be printed in black and white and easily photocopied anywhere.
I know we also did one for OSCON 2005 in Portland, but I don't see a copy around anywhere. I'll try and track it down.
I made a placeholder page on public dev wiki if someone wants to start writing: https://svn.bryght.com/dev/wiki/Drupal/Marketing
OSCON 2005 (Portland) - Drupal 1 pagers and booth banner
I've attached the one pagers (black and white and colour) and the booth banner to:
https://svn.bryght.com/dev/wiki/DrupalOnePager
hopefully this will help the DrupalCon EuroOSCON 2006 one pager and booth effort
Here are the direct links:
Claim
Sorry, but is this really the designated claim for Drupal?
Daniel F. Kudwien
unleashed mind
Daniel F. Kudwien
netzstrategen
Fun at OSCON2005
No, it was a fun slogan at OSCON 2005. We gave one to the Plone team that was attending, and generally had a lot of fun with it. It's not an "official" slogan.
i think it came from chris messina
or at least he was the first to bring it to my attention!
chris worked at civicspace and did lots of Drupal themes, then he worked for Flock and now he's a free agent:
http://factoryjoe.com/blog/
Why We Chose Drupal
Here is a quick dump of a slight dated article I wrote for Ashoka on why I recommended Drupal...
Starting in July 2005, I was hired by leading citizen organization Ashoka (www.ashoka.org) to develop a
content management system that be would used to host online collaborative competitions on multiple sites, and potentially also be used as a larger knowledge management system.
After some investigation into the user needs with Ashoka and their partners at The 215 Centre for Social
Innovation (www.the215.ca) I created some detailed mock-ups (http://www.1org.ca/siawards/) and extensive
user case scenarios.
Based on this research and planning I recognized that some of the key required features of the project
include:
As well, the system had to be easy to install on common Linux server configurations, secure, scalable for
thousands of users, flexible for future modifications and open source for sharing with other social mission
organizations.
Rather than create a new content management system (CMS) from scratch, I decided to use an established
open source application that could be tailored and modified to meet our needs. This way we could pull from,
build on, and contribute back to years of community software development. The big question was: of the
hundreds of open source CMS applications out there, which one would we use?
After some investigation and comparisons on www.cmsmatrix.org, I created a short list of...
Drupal: www.drupal.org
Mambo: www.mamboserver.com
TYPO3: www.typo3.org
WebGUI: www.plainblack.com/webgui3
Co-op Tools e: info@cooptools.ca p: 416-538-2667 1-866-519-2667 Page 10 of 12
(file: Ashoka_Multi-site_Drupal_System_Contract_1-01.doc) Page 11 of 12
Xaraya: www.xaraya.com
Each of these applications seemed to have highest potential for fulfilling the requirements, although no single
one was perfect.
To make the final decision I sent emails and posted messages to developers of each application asking
specifically for examples of sites that demonstrate scalability, multi-site deployment, multi-lingual support,
granular privileges, customizable workflow and customizable databases. From my experience, if the
developers can not provide a working example of the feature you need, than chances are it's still a long time
coming.
The results of my investigations and discussions with developers...
For TYPO3, the customizable databases would have to be a new extension, which is more development work
than I had budgeted for.
Mambo had nice usability, but developers said that is had limited flexibility, difficult customize and granular
privileges and workflow were "coming soon".
WebGUI's workflow engine was "still in progress" and the customizable database required authoring SQL
code, which would mean either a barrier for most users, or require extra development to make a usable
interface.
Xaraya seemed to have a lot of potential and great flexibility. Although a newcomer to the CMS scene, the
developer community seems to be quite lively and the feature sets are good. Beyond some limitations around
field sorting for the database option, my main concern was that I did not know personally of any
organizations or developers using the software, which I do for all the others. I had concerns about my ability
to find experienced developers to support it.
Drupal become an obvious choice for many reasons:
personally know many developers that use it for popular web sites and praise its capacity.
user tracking and decent granular privileges.
www.levavie.com
http://drupal.org/project/Modules
Co-op Tools e: info@cooptools.ca p: 416-538-2667 1-866-519-2667 Page 11 of 12
(file: Ashoka_Multi-site_Drupal_System_Contract_1-01.doc) Page 12 of 12
See current project in progess at https://trac.ashoka-dev.org/
Jason Diceman - Co-op Tools
One pager revisited
Just before DupalCon Brussels I saw a topic by Boris Mann about a Drupal one pager (Can't find it anymore but it was based on this one at Bryght). I had a look at it and thought it could be improved visually but also from a communication standpoint. So the night before I leave to Brussels I quickly hacked the pdf file in Illustrator. I showed the result to Boris, he liked it and suggested I post it in this group.
Apart from the visual design, here are the gripes I had about it :
So, here's my own take on the one pager.
I added silly names under the quotes, don't pay attention ;)
I've read there is not much marketing material at the moment. As it seems more will be written, I think there should be a set of "rules" to make it easier for writers. Perhaps not a whole graphic charter (yet), but at least a few simple guidelines to help give a common look to the documents. Has anybody done this before?