In the past months I've been doing a lot more graphical design, and it's caused me to think about how it relates to Drupal. This prompted me to write a rather long blog piece with some insights and a call to action. If you are interested in the future of Drupal, please read on.
The trigger was that I noticed that I'm getting less and less motivated to do graphics work for Drupal. It's not that I don't like design... I loved designing and building that LeuvenSpeelt.be site last month for example. But when it comes to Drupal graphics, the personal reward that I feel from doing it doesn't seem proportional to the effort I put in. This includes designing little banners for the Drupal.org spotlight, doing a t-shirt, making ad buttons, doing the association theme and more.
The most recent big example was the Garland theme. When Stefan Nagtegaal showed a work-in-progress version of his 'Themetastic' theme (as it was then called) in September, I was instantly charmed and knew that this was our new default theme in the making and said so clearly.
Many others were not convinced though and hammered on details, even though the basic design for the theme was rock solid. Some were not convinced of the theme's potential, or simply didn't see that we needed a theme that was graphically smashing rather than a good base to develop on.
At that point, I essentially said "screw the community, this is going to be our default theme" and started refining the theme so it was perfect for core. This took several weeks.
Until then, the rest of the community put its eggs in the wrong baskets and got a lot of useless design-by-committee done. These designs, which were in my opinion mediocre at best, were being pushed for inclusion. This may sound a bit harsh, but I honestly believe that if the most popular candidate theme, Deliciously Zen, had become the new default core theme, we'd have been ridiculed for still not 'getting' design after 6 years and Drupal 5 would not have been such a big release. Just like 4.7, most people would not stick to Drupal long enough to discover how good it is.
Now, when the Garland theme was finally done, everyone suddenly changed their opinion and congratulated the community on its excellent work. I have to admit this hit a nerve, especially after I'd been spending countless days and nights the two weeks before fixing annoying IE rendering bugs, redoing the CSS layout and adding a whole new layer of Glitz und Glanz to Drupal core.
Only three people did serious work on what became the Garland theme: Stefan Nagtegaal did the original design from scratch and worked with Adrian Rossouw to come up with a proof-of-concept of the recolorable theme. I wrote the color picker, improved the theme and coded what became the color.module based on Adrian's stuff.
Only a handful of people helped with testing of the theme during its development and only after the main theme was finished — most of the bugs were in the recoloring mechanism. How can such a vital piece of Drupal 5 have only have 3 serious contributors, when the whole release had almost 500 people submitting patches?
To me, this shows that we have a problem in the Drupal community, or rather a knowledge void. Not enough Drupal people are savvy enough about theming and design to help out with even small tasks (like a banner) or even give quality tips and feedback on other work. The result is that theming and design receives little attention. Most contributed themes and sites could look a lot better, if they just themed it some more. And getting patches into core that give the defaults a little more oomph is tough, as they are often considered to be useless embellishments.
Still, ever since Drupal started, there has been the recurring cry of doing more to attract great designers to the platform. The overall effects of this have been minimal. However, something similar did happen before.
Before Drupal 4.0 was released, the focus was mainly on features and Drupal was a highly experimental project. After a while, as more people started using it, many users complained that Drupal was too hard or confusing to use. Because of this, 4.0 was the first of many releases that contained significant usability improvements, in this case in the administration area. Many small and large usability features were added. With the menu system and tabs having been added to core by Drupal 4.5, even contributed modules started using the same UI concepts as core. Drupal's UI ended up much more consistent across configurations and it became easier to learn and document. Now with Drupal 5.0, we have undoubtedly produced the most usable release yet.
How did this happen? Over the years, the idea has popped up many times to bring usability experts on board to do a review, and the hope has lived that a usability expert or two will magically pop up in the community and solve all our problems (sound familiar?). Neither has happened so far.
What did happen is that usability became a big priority for the project, and as a result, many people started educating themselves about it. The community quickly identified those in its ranks knowledgable about usability and listened to their advice. Soon, big UI gurus were being quoted on the mailing lists and "-1 isn't usable" became a valid reason to dismiss a feature. Sure, this process took time, but it definitely happened. Plus, the combined usability knowledge and effort of the community, though individually not at expert level, had a much larger effect in the long run than any single expert could have.
The same needs to happen for design. For years now, the Drupal community has been hoping for a group of prodigy designers to magically appear and design a set of jaw dropping themes and UI. They have not shown up. Talking and maintaining a high quality of design across Drupal still often feels like swimming upstream, because most community members don't care much for design unless it is delivered in front of their noses on a silver platter. For many, design is still something to only be enjoyed, not something to be created.
Now, I really want to see this change. For one thing, the shortage of design talent means Drupal is generally perceived to be ugly. It's quite demotivating, because we put a lot of time into it. Unfortunately people illogically, but consistently, assume a relation between how something looks and how good it is built. With Drupal 5 we've done a lot to improve this, but we could still do a lot better. Drupal is no OS X (yet).
For another, when only a handful people are always doing the same jobs, the passion tends to slip out and the challenge becomes a chore. I honestly have no ideas left for a spotlight banner at the moment. That's why the scalability banner is so mind-numbingly boring, though I made plenty of cool ones before.
This is also why I'm holding that OSCMS talk about design this month: I want more people to realize that if your site and/or module is ugly, people aren't going to like it or use it. It's as simple as that. If you mess up something as basic as text formatting, your message simply doesn't get through (hello MySpace users). The only way to change that is to put in the effort to make things look clean and nice. Nice products and nice sites tend to cause happy, dedicated and long-term users.
The community not only needs to realize this, but also needs to teach itself the knowledge and skill to do something about it. Drupal has infinite potential, but it only goes where the community takes it. If the majority remains allergic to design and graphics, very little will change and only at a glacial pace.
Drupal designs
I'm writing as someone who has followed the Drupal development for about 4 years now. I'm neither a developer or a designer. Maybe "advanced hobbyist" would be a good description. I do have education in both programming and information design, however. And now that we are looking at Drupal in my school as a possible website solution, I'm really paying attention!
I would have to echo Steven's comments about Drupal being seen as "ugly". Obviously it's not fair; you can do amazing things with the design of Drupal (witness Steven's theater site). Drupal's strength is its interior architecture -- absolutely amazing stuff. That stands to reason, since almost all of the Drupal people seem to come from the development side. Developers sometimes don't see the need for a good design for the interface (I've heard some refer dismissively to design as "pretty pictures"). But information design is much more than "pretty pictures", and even more than just "usability". Color, placement of text, fonts, balance of objects, etc., all play a role in making the user experience not only pleasant, but efficient.
I don't have a solution for this. Like Steven, I hope that some great designers will magically arise (it's happened with Joomla). Perhaps the usability and user-friendliness of 5.x will help eliminate barriers to entry for those people. There has definitely been improvement in the themes available. We need mutual respect between the "prop heads" and the "ponytails".
Agreed...
I agree with you. We need to learn to be designers. Personally, I am an engineer and just don't have that artistic touch. I would love to learn to make better designs. Is there any chance you can post that presentation from OSCMS online somewhere? I am sure it would be a great help to a lot of people.
The other day a couple of us were talking about drupal is ugly. I think this may be the single most important thing with picking Joomla! over drupal.
corporate designing
I'm only following Drupal since the end of 2004, but I am convinced that great design, i.e. designers, will not magically arise. Designers have another spirit then software writers. I quote a teacher at the graphical department here in Gent (Belgium): "My students do not wish to work together, they keep their ideas and work for themselves". I don't know whether that's true for most of the designers out there, but it indicates that designers think/work differently than oss people.
But now and then, you have software writers who can not only code well, they design too (2 x Steven, Chris Messian and some others). And since they have the OS spirit, they share their work.
Anyway, my idea on this: perhaps you should address this post to corporations rather than the community. They are paying designers to make a nice theme for their site. If they would contribute it back, it might make a difference on the long run. I believe that the Spread Firefox theme was contributed this way. Correct me if I'm wrong.
How About a Theming Contest?
I am working on my second Drupal site now and have spent quite a bit of time designing and now building my theme. (I'm not a designer, but I'm learning fast...)
At one point, I considered giving up and using Wordpress. Then, a funny thing happened. I had gotten so familiar with Drupal, that theming Wordpress seemed harder. So, I'm back to my original plan.
The key, I think, is getting people with a design background interested in Drupal in the first place -- and past the belief that theming is too difficult in Drupal. Then, they'll stick with it an contribute. I'm not sure if just anyone can create beautiful graphic design. It takes an artistic sense. So I think such people have to get involved.
Perhaps a theme design contest with some kind of prize would do the trick? I'm a PR guy and that's what I would do to generate interest.
I believe it worked well for Wordpress.
Hear ye, hear ye
I think you're championing a great cause, and it's great having someone with a strong aesthetic sense and realization of its importance in Drupal's upper echelons.
I think some clarification is in order, though. By "designs", do you mean gorgeous front pages, do you mean contributed themes, do you mean the actual Drupal elements (that are often unchanged and commonplace) like comment forms and search and content creation screens? Probably all of the above?
I think you'd like to see a theme that handles the front page display differently, perhaps utilizes Ajax techniques where appropriate, and (most importantly, IMO) really takes advantage of the powerful theme overrides to make all the input boxes and Drupal generated elements much prettier and usable and cleverly positioned. So would I. But then, this would become everyone's theme, and that's rather boring.
I think you'll see designers do such a thing for their own projects much before you'll see anyone contribute all that to the Drupal community, and they can't be blamed: The look, the design is what really differentiates one site from the next, one workflow from the next (often theming CCK + Views versus a whole theme) and so effort there is effort spent on one's own site. Contrast that to the underlying code, which is the engine, and it's ok for everyone to use the same engine, and for developers to contribute back to that common engine, because it's under the hood, and you then get to paint your hood a different color, if you will (though many don't choose to or can't). Part of that has to do w/ the complexity of code and a powerful system like Drupal -- it just makes sense for everyone to work together on that beast, while design is more of a differentiator.
I think there certainly needs to be more knowledge of the theme system in Drupal and its power. Maybe better documentation would help, hopefully the new Pro Drupal Techniques book will help, and certainly more committed and involved users would help. But I imagine we'll see design work applied to individually owned projects before we'll see it applied to the community. That said, it inevitably helps the community in numerous ways, anyway -- by demonstrating better Drupal sites, showing what's possible, generating snippets and techniques and knowledge, and possibly improvements to the theme system.
Me? I think Drupal should really focus on being a content and community management system and focus more on informational display while of course allowing all that to be themed well. I think Drupal largely takes that approach, and CCK and Views are great in that arena. I personally would love to see a theme that used Ajax techniques to grab information w/o refreshes... like the Gmail interface. While we're talking, I'd love to see a real messaging interface so every module sent e-mail notifications or internal notifications (like moderation queue, unread messages, etc...) cleanly via one channel. Let's focus on Drupal as a system versus Drupal as a pretty brochure-like site.
Sorry for the ramble. More to say later.
--D
Great commentary.
The joy of coding Drupal far outstrips the pain of CSS and browser compatibility. Every time someone complains that Garland has such-and-such a problem in IE6, I want to kick them in the head.
Lots of small steps...
I agree
I just recently (post 5.x release) converted from self-produced CMSs to Drupal and I'm loving it (1 site running and 2 in development). And that's mostly because of the Garland theme, because if it still had the theme of 4.7, I wouldn't even consider Drupal even though it has a great themeing system with high plasticity.
I a little bit doubtful whether the growth of the usability knowledge within the community is a good comparison of what will/should happen to the design knowledge. Usability is a concrete subject that can be read about, learned and transfered to other people and applied. Designing a graphical enjoyable and beautiful website/theme is a trade, it's not really knowledgeable. So in stead of hoping that people will eventually become the best designers, it's more a need of trying to get already great designers
to work on and with drupal. How?
Well there are a few initiatives out there called operating with the intention of creating Open Source Webdesign (http://oswd.org and http://openwebdesign.org), that could be of assistance. They have a big user base, of which a few are quite talented.
Also, what farrell said above me: issue an design contest. On a few commericial webdesign forums I visit, these are often very succesful. This is of course not free, but generates often a lot of good work, although you'll have to reach the right audience of course (so not just drupal.org). If it doesn't result in great designs, at least it grew some awareness and interest in the design-part.
And last but definitly not least: contact the pros, especially the companies that are using drupal as their main CMS for their customers. Ask people of designes promoted on sites such as http://unmatchedstyle.com to lend a hand. It never hurts to ask, right?
Maybe it's a nice idea to dump your story at the designers group @ drupal.org. Because that group is kinda silent and it should be the one that is working its butt off to relieve to small number that are currently doing all the work.
BTW, as I said, I'm new to drupal, but very enthousiastic about it. Besides a programmer, I also design quite a bit. As bug fixing and porting old modules can get boring at times, I wouldn't mind helping the designteam out. Where can I keep informed about what needs to be done (for example those flashlight banners you mentioned)?
Left brain, right brain
Good points. I think Dave Notik's point about code being universal but design being unique also is a great insight. I can feel for you re the Garland development. Design is hard enough without a world of critics harping on every detail. (The outcome is pretty nice, and your color widget is simply awesome!) I tell young designers: if you want praise, find another profession, or do it for the love of it and ignore everybody.
It seems to me that one of the biggest impediments to getting more design work contributed to Drupal is CVS. Let's face it: designers are not coders. Most of the designers I know have no background in programming, and the arcane mysteries of CVS are simply not in their ken.
Beyond that, I think a large part of Drupal's challenge for a designer is its power. Theming for so many different kinds of content is way way beyond what's needed for most other "web 2.0"-type platforms. There are quirks and frustrations that persist, from non-semantic embedded css to un-tagged UI elements that force themers to resort to phpTemplate overrides -- i.e., programming -- but from my perspective it's getting better with every release.
Still, while it can only help, I don't see a call for programmers to think like designers getting us very far on making Drupal not "ugly." Usable, yes, but beautiful? Design is right brain and programming is left brain. While some people can excel in both, most people are predominantly strong in one side or the other. Really, if we truly want Drupal as a platform to excel design-wise, I feel we need to make the Drupal community more accessible and welcoming to designers. I don't know how, exactly, but most artsy types aren't going to dive into self-education on CVS in order to give away design that others will say sucks -- and those who do are going to run into roadblocks every time it hit the unavoidable program code required to do x.
Trying to help address that goal was the inspiration for proposing the theming session at OSCMS -- trying to make the theming process a little less mysterious to the geek-inspired but not necessarily code-savvy Drupalers.
I do take heart, though: Your sessions on design and jQuery and our session on theming are the top 3 favorites on the OSCMS voting to date. There's no denying there's interest in the subject.
As somone....
...who started off 10 years ago as a print design/production manager at a printshop which was only a couple miles away from CalArts (one top three design school in the U.S.) in southern California, and then went to working as the online production manager for the former head illustrator of MacWorld at a design/ad agency in San Francisco, and am now trying to bridge the gap to being a full-fledged Drupal developer I definitely feel identified with that part of the world. (*I claim only to be of the 'junior/layout designer' caliber - I'm definitely not a 'true' designer)
Honestly, from all of the 'true' designers (those just talented at birth) I've ever known - here are a couple generalizations:
I'm not sure if anyone will take this suggestion seriously or not - but if the Drupal Association wants to help promote the Drupal platform and advance it's visual/aesthetic perception it would do well to commission some artists to provide photoshop files and then have members of the Drupal community 'Drupalize' them.
Alternately or in conjunction, the Drupal Association could sponsor a design contest in which the submissions were given as photoshop files to be converted later.
The point which is hidden in those suggestions, and which I really believe to be an immutable truth, is that it will always be extremely rare to see true design specialists ever take the plunge into *any* code, let alone validated code, and/or Drupal.
I couldn't agree more, Design is Important!
You hit the nail right on the head. When I first started using Drupal ages ago I was instantly drawn to it because of the programmer in me. However time after time, I wished that the Drupal community was a bit more designer friendly. Though the programming aspect of web design and applications is important design is just as crucial. In the end Joomla seems to get the very best of the CMS designers and Drupal the very best of the programmers.
Sorry to not get this in the other post...
but some links to better illustrate the difference between - 100% bonafide, credentialed, educated, and ridiculously talented/cutting-edge graphic design and what the Drupal community as a whole currently consider. These are the kind of people Drupal need to reach out to if they want to promote the aesthetics:
Drupla themes are great foundations
I believe there are two ways to look at themes:
1. A theme can be solid foundation to build your custom design on.
2. A theme can be a beautiful design out-of-the-box.
For people like me – and I would hope most web developers – I don’t care about #2. Whatever the theme is, I am going the radically change the look of it anyways.
I care a lot about #1. And from my experience, Drupal has no problem with #1. By the way, Zen is an excellent foundation theme. I also use Burnt a lot.
Joomla (for example) clearly beats Drupal on #2. But who cares? It is mind-numbing the number of different designs there are for Joomla – and just gives me a headache. Give me a handful of great “foundation themes” over thousands of designs any day.
Drupal core is all about being a rock solid foundation – and I see it as no different for Drupal themes.
I am sorry about all the problems with developing Garland - its awesome, so thank you for all your work on it!
Art takes authors
Design by committee generally doesn't work. It doesn't work for modules either.
Your point about the lack of useful feedback from the #drupal community on design ideas (vs more useful feedback on engineering questions) is insightful, and seems correct, but don't loose sight of the fact that great themes or great designs generally spring from a single individual's creativity.
That said, having more of a community emphasis on beauty and usability would be a good thing.
I think Drupal can continue to do more to improve the admin UI -- which is already getting better -- and extend those improvements for contributed modules that want it. The foundation is there in Form-API; all that's needed are more examples of "doing it the Drupal way."
As for front-end stuff, it's really a matter of getting more artists involved. Beauty breeds beauty. This is a different motivation for people than the idea of "theme = foundation." There's room for both, I think.
Professionalism
If I can defend "'true' designers" out there for a moment (heh) .... Caleb, it sounds like you're describing people who aren't professional in their work ethic, and that can happen in any field as a symptom of personal failings sometimes, but in my experience is more often the result of poor management and/or education. I don't feel graphic design is particularly special in that regard, except that so many of the schools out there seem to be woefully under-serving and ill-serving their students by not teaching them (a) how to criticize work, (b) how to take criticism and (c) how to work the critical process into creative work both personally and collaboratively ... not to mention continuing to push Dreamweaver as some sort of professional web design skill (ha!) while not teaching CSS (one of our major frustrations as we go through resumes of recent design graduates).
That said, I think appealing to the design-centric worlds out there is a positive idea. I don't know if contests are going to draw many -- after all, so much of design isn't competitive, it's expressive -- but somehow working to make Drupal less obscure and opaque to designers would be a definite positive development, imho. Maybe just having contributions on just the design comp level would be a start (and add fivestar voting to it to add competitive flavor for kicks)?
Being part a designer I
Being part a designer I agree with Rick Hood about this. From a designer point of view I couldn't care less about Garland since I would build my CSS from scratch anyway. And from what I've read Garland isn't even a good starting point if that's what you're doing.
But Garland is oh-so important for appealing to people in general, it's delicious ("lickable" to use a phrase from Steve Jobs) and way beyond Blue Marine as a face to show Drupal off.
(Being a Mac user for a long time it's apparent that what sets Apple apart from many other companies is that they "get" design, all the way up to the top of the leadership. That good design is more than just a fancy look. The usability improvements of Drupal is sort of a design thing to, but the good look is of course the main part.)
It's one thing to make a good-looking theme for your own creations, and a whole another thing to release it as an all purpose theme. It's an awful lot of work to make a really good and well working theme and then you have to support it as well. Maybe that's what is keeping designers from doing themes for Drupal?
+1 on the contributed design comps
This is a great idea, Laura. Additionally, people (myself included, naturally) can make handbook page to direct people to resources like this.
Just want to be clear that I don't disagree with your points about professionalism. It's got to be hard for students to get the information when the information is slow in getting to the teachers though. For instance one of the premier teachers at that school was a gentlemen by the name of Ed Fella. He's a world famous typographer. And he wouldn't know a computer from a boat anchor. Whenever he brought in stuff to be printed it was mechanical hand-drawn artwork. That was '99, so maybe things have improved since then, but yowsers - what a starting point!
I agree with most of what
I agree with most of what you've said, Steven - with the exception of:
For years now, the Drupal community has been hoping for a group of prodigy designers to magically appear and design a set of jaw dropping themes and UI. They have not shown up.
The fact that you're a huge part of the community, and have been a critically important part of the group that produced the Garland theme (which continues to be jaw-dropping to everyone who actually uses it for more than a minute or so) shows that just such a group has shown up.
I, for one, really hope that you can put up with the cr*p and can continue to show the rest of us how well it can be done. I can't design for nuts (and my coding is probably at best something to be avoided :)) but I do appreciate and recognise good design when I see it - and have some feeling for the effort that's gone into to making it look like there's been no effort at all.
Garland is a wonderful piece of work. It has shown that Drupal can have beauty that's "skin deep". And that lets more people get to know the beauty that's hidden inside too. What, I think, sets the 5.0 release apart from what's gone before and everything else that's out there is that it's good all the way through - and a large part of that is due to Garland.
So please don't stop. We (the under-talented and under-appreciative of the community) need you :)
Let me quote
While I try to educate myself in interaction/interface design but graphics does seem like arcane voodoo magic. I will be delighted to listen to your presentation in SF as you dispell this myth.
Design Talent
I don't think a design contest will work that well. As has been said, making a generic Drupal theme is simply an order of magnitude more complicated than e.g. a WordPress theme. In fact, designing for Drupal requires a shift in thinking for most designers too: Drupal is simply a very powerful system that goes beyond what any individual site does.
Plus, even if we do get some finished designs that style more than just the bare basics, that does not guarantee that the themes will be maintained. The only way to ensure themes get maintained is for more people to know HTML/CSS and design.
Here's an analogy: someone contributes a patch, but it is found to decrease performance quite a lot. If all the reviewers can say is "It's too slow", nothing will likely happen. But if they say "It's too slow, take a look at optimizing these queries and maybe implementing some cache for these objects", it's likely to be improved and committed soon. However, in order to give this sort of feedback, the reviewer must be familiar with all aspects of software design.
Trying to review a design, when you do not know much about layouts, colors, composition and typography other than what your taste tells you, is completely analogous. It is this sort of knowledge that is lacking. Would you review code purely on taste, without facts to back it?
I don't expect that after I give that design talk, a room full of Picasso's will walk out. From Drupal 4.0 to Drupal 5.0 took us nearly 5 years to spread usability skill and awareness in our community. I just hope that it will set in motion a similar process and introduce the principles and vocabulary that designers use.
Also...
joshk: Personally I think some designers would benefit from getting out of their ivory towers and realize that working together with others can often result in a better design. Design by committee generally goes wrong because there is no single vision or idea, not because it is inherent in the process. For example, when I took Themetastic and turned it into Garland, my goals were clear (and I told Stefan that):
These were things that were required of a generic, default core theme, and which were not 100% there yet. But I don't think I touched the basic idea or design of the theme that much.
It also needs to be pointed out that doing any sort of work (be it code or design) in group necessitates extra work and process to succeed.
Brad: I don't think designers magically popped up. Me and Stefan have all been long time contributors. I've seen Stefan do Drupal design over the past years, and I've clearly seen his abilities improve too. I think you can see the same evolution e.g. for every edition of my LeuvenSpeelt designs. It's a long process that takes work. My point was that if nothing else happens, the few skilled designers will get tired of being the graphics gimps-du-jour and Garland will remain a one hit wonder that slowly dies out.
Laura Scott: I'm very aware that design is a 'trade', but I still think that lot of the geek/designer opposition is an irrational one and that designers will never feel welcome in the community unless we 'walk a mile in their shoes'. I do think that teaching design to geeks needs to happen differently than to designers, which is exactly what I intend to do :).
As for presentation slides: I'll put them up when they're done and the session has passed, but I don't want to make them available unless the video or at least audio is there to accompany them. Many of my slides are just large images with some circles to indicate things I talk about, and a lot of the message would get lost.
Keep up with the good work!
Garland is a great theme.
It is not easy to be good designers indeed, but it is very easy to recognize them from their work.
I agree with all who think that a group of great designers has shown up.
When I was looking for a CMS, I learnt of Drupal by reading the following statement in a blog comment written by a professional:
I disregarded the second part of the post and tried Drupal anyway. In a few hours I became passionate about it.
The post dated 11 March 2005. Meanwhile, in just two years, the 'face' of Drupal and its usability have been greatly improved.
I am sure that she would write no buts in her comment now.
Thank you and keep up with the great work.
learning curve...
Just to throw in my approach to this drupal & design...
First off -designers will never get as many kudos points in an coding environment, it will always be some kind of black art : what we are doing whith photoshop, as well as drupals menu code is way beyond what i understand ;)
The biggest step as a designer as i see it, is actually the learning curve. Drupal is easy (kinda) to get started at: fire up the 5.1 with the standard theme and your up and running with a nice design in no time.
But is dosnt like WP tell you what to do - afaik only a user who wants so create a blog is downloading & installing WP, when you get drupal you must actually think - then lets say this user know what he wants to create a site for the local sport club, he installs drupal, get some moduls, and get a theme or two, if his a tech dude - well my guess is he says: we got all the functionality, and i looks nice - so my work is done...
Well if his like me, then before he even got to the point at thinking bout php & drupal he got a bunch of design draft all layed out - and then its very hard to se how drupal can do all the magick stuff, unless you know about cck, views, image cache etc
When it comes to getting the designing from photoshop to drupal - you have to get into this theming stuff, and if it wasnt for the last 5 years with a php manual at my desk, i would have been totally lost (i cant even count the times i did print_r($foo) the last 6 months to get som idea bout WTF is going on)
The learning curve to get into the theming is for "normal" web devs. not an easy task, what i have been missing the most is some kinda "how to implement a design in drupal for dummy.. eeh designers" pdf
I mean last week i used 2 hours clearing my cache and whining about drupals cache, until understood that drupal defaults loads page-front.tp.php as a the frontpage template
To lure more designers to drupal i think we need a more non-technically approach to the theming part, something like a 10 pages how to would kick ass.
As fare as getting props from geeks who cant se that pink & yellow looks like shit together -well that will be a never ending struggle ;)
and just to be clear I have the most respect for the huge work these übercoders are creating - at a daily basis im like "wow i could do that".
Maybe this is the call for creating a designer work group? -so we can cry at each others shoulders, and talk with somebody who actually gets why Helvetica rules and arial sucks ass :)
finally :)
The best Open Source marketeer, Shuttleworth, sums it all up: http://www.markshuttleworth.com/archives/63
« Of course, “pretty but unusable” won’t work either. It needs to be both functional and attractive. Rather than bling for bling’s sake, let’s use artistic effects to make the desktop BETTER, and obviously better. »
Drupal faces this in tenfold. Every 'prettyness' that comes in the box, may give people the feelign that the WoW has started, but it has a fair chance of taking possibilities away from those that don't need that wow, or those that need to build their own.
In Drupal we see a Foo Vs Bar popping up in every such issue: Drupal needs to make choices, and when its not possible to make something that is both Wow and cutting edge, then the cutting edge will win. Drupal has, whether we like it or not a (very unhealthy) disbalance on the technolgical side of matter.
How often patches for 'simplifying theme_foo' have been hammered down because they 'performed less good', or another pure technical reason? I lost count. How often themers have asked for consistency in ID schemes, or at least something that makes module and core developers /think/ about the ID, classes and XHTML structures? I lost count. How many themers have complained over and over, that many theme functions are simply far too complex? I fon't know anymore. The answer to all is 'a lot'.
But just like with the usability stuff, that horrible 'code not talk' mantra shood away every attempt of people into design (or usability) within hours. Designers don't make patches. when we (that is all of us, most importantly the module developers) finally understand that, we might actually get some mechanism going to include the effort of designers and themers into our workflow.
I am very happy that after years of ranting from my side, I finally find a heavy weight Drupaleer 'really going for' my pet peeve: making Drupal a place for Designers (too). A historical moment!
Why is it an order of magnitude?....
"As has been said, making a generic Drupal theme is simply an order of magnitude more complicated than e.g. a WordPress theme."
As a long time Drupal user/webmaster, I've seen the coming and going of themes... including themes designed to use wordpress themes/css, allowing lots of options.
My favorite themes (and as I've used dozens of themes, my favorites have evolved) are the ones that do a good job in separating the css bits, making it easier to change colors without messing with layout, to change one type of block without changing the others, etc. In other words: the better done and _labeled_ the css separations, the easiest to customize. (Never mind that it has to work with IE and Firefox, use minimal or (preferred) no tables, and be flexible or fixed as the client wants...)
We need more of this direction. We need to make it easier to customize, not harder. Why does it feel like so much of the community (or individual) efforts in 'cool' themes just end up making it harder, not easier, to move in this direction? Zen and others are a step in the right direction, but not far enough a step. That (IMHO) is why doing a Drupal theme is 10x harder than a WP theme: because we lack the good clear _supported_ examples to model from, and base on....
Sympal, Zen, Box_grey, these are examples of the right direction... yet, compared to the 'port of WP/OWD theme' that 90% of the themes on Drupal are, it's no wonder we don't have a thriving community: too many have to reinvent the wheel each time.
If you want to do a useful contest, make it a Zen Garden contest - provide cssing (and tpl.phping) for this bare but fully functional Drupal theme (use Zen or make a new cleaner one). Bonus points for improving the bare theme for everyone else to use as well, so that the community benefits. Inside of 6 months, we'd have more original themes for Drupal, and better yet, we'd have a stronger generic base theme.
Tableless CSS
Have you tried making tableless CSS for a serious CMS like Drupal? It's not as simple as when all you have to accomodate is a list of blog posts and comments.
Plus, generally Drupal users tend to be more demanding of themes. When Garland got ported to WordPress (by Matt Mullenweg himself no less), it lost its ability to be both fluid and fixed, and to have either sidebar turned on or off. The navigation abilities have also been reduced (no secondary links).
Drupal users expect these sort of things for themes, and complain if they don't work.
The simple fact is that there are loads of well designed Drupal sites out there (Zimmer Twins, Terminus, ...), but that the effort needed to make a generic, reusable, flexible theme is something that very few people are willing to do. Just sharing a single site's design isn't enough.
Why is it an order of magnitude?....because
When you do a Wordpress theme, you are essentially building a blog theme. You have a known target. You can make several broad assumptions on the type of content and decide on it's layout.
With Drupal, will it be a blog, a corporate brochure, a community site, an eCommerce site? In order to build a theme, you sort of have to design around unknown content and account for a wide variety of use cases. If I have sections that are to be themed differently based on url how do I easily write that up?
Theme is based on content. It is easier to build a site for content you know then to build a site for the unknown and account for such a wide variety of possibilities.
About the Drupal divide…
Hi Steven,
I want to congratulate you on your work – the LeuvenSpeelt site is beautiful. I'm not a member of the Drupal community or a traditional designer, but I have a few thoughts on this.
Drupal's functionality is unparalleled, and I think you all are the best PHP developers around. I'd like to echo the sentiment that there is a steep learning curve. I think Drupal is just a bit too powerful and complicated for most solo designers and small firms: you have to be a server administrator, PHP guru, database admin, designer, CMS/info architect, and CSS/XHTML expert all in one – not just good, but truly expert.
All themes do, really, is take away some of the front-end work by making the product easier for non-designers; meaning, either non-artistic developers or non-techies. The former will benefit immensely – the latter is still stuck trying to deploy and manage Drupal.
Most designers will hack a default theme immediately – that's what I did on my first Wordpress install -- I could instantly bend it to my will. But, I'm not ashamed to admit it…I haven’t even successfully gotten Drupal installed yet. Tried twice (4.7.3 and 5.0 beta) on my shared hosting account (without shell access), and then most recently finished grappling with setting up virtual hosts on XAMPP.
I'm getting there slowly, but all of this takes time away from designing, content planning, and focusing on the client, and that's something most of us can’t afford. Time is money, and with this kind of up-front investment, there isn't any incentive for people to freely share out the fruits of their efforts. Rather, success becomes the eminent domain of those few who can jump the Drupal divide by being both exceptionally creative and technically adept at the same time.
I think Drupal works best in team environments. More real-world collaborative projects might be the key to demonstrating its capabilities. I'm happy to serve mine up as one if the Drupal community is interested.
Reducing the order of magnitude
Steven and Sepeck,
I am not arguing that a complex situation requires a complex theme.
Yes, it does.
Yes, a simple blog is easier to style than a complex community site.
Yes, tableless css is much harder for complex layout situations.
(eg. try finding examples of 4 column css layouts... rare indeed)
Yes, subtheme styling can entirely change sections of a site...
Yes, good generic themes are hard to find and few are willing to do it.
All of these are arguments in favor of my "challenge" to do so as a contest, rewarding (with kudos [and/or donations or design consulting work potential]) those who contribute to the task.
A good generic theme will have the ability to deal with the various modes. Thanks to CSS, and drupal's amazing ability to subtheme, these modes can be layered. Make the contest address this, by having (to use your examples) Blog, Brochure, Community and E-commerce categories. If there is a nice basic template set for each, a designer merely has to have css to fit each (or all) of them....
If layout, color/etc are properly separated into imported css styles, then ideally, I can pick a (matching hopefully) layout for each, add the same color/etc stylesheet for the entire site, and the site should look decent enough no matter... not perfect, but the goal is to get 95% of the way, and let people customize it for themselves...
Subtheming by url/taxonomy tends to fit one of the above cases usually, but let's add the idea in and make it a 5th type of layout: Special, to catch any cool tricks people want to write that don't fit the others. In a realworld situation, you might use 2or 3 'Specials' for parts of a custom site... but the goal is to allow creativity here... Special would allow custom CCK templating examples for instance.
A video sharing site (for example), or a digg clone...
Lastly, let's split off (and encourage) the sort of 'theme emulation', for those who don't have such high standards. And that should free up the designers who spent time porting Wordpress themes right now...
If the 'clueless designer who just wants a pretty blog, and wants to unpack and go' will be happy with less, they can find lots of themes out there, done by others...
For (older?) Wordpress themes:
http://www.7gen.com/book/content-management-systems/css-based-themes-dru...
(someone should port to 5.0, it's for 4.7 right now, and get it into cvs)
and for MT-based themes, see http://drupal.org/project/gutenberg
Ranting and attracting design talent
Steven,
I wholeheartedly agree with your thoughts. Drupal's number one pitfall is the lack of quality themes and designers. The project is developer centric which is a shame as it isn't REALLY that bad to theme once you know what you're doing.
I remember talking with you about Wordpress and why there are so many great designs available for the platform. One reason that you gave is that designers only have to worry about two pages - the blog listing page and the blog post itself. This makes the system easy to work with on a technical level. Drupal, on the other-hand, is much more flexible and therefore themes have to take into account all types of other variables such as the modules enabled.
While theming Drupal is a bit harder than WordPress I think the real reason that designers stay away is their first impression and lack of awareness in the blogosphere. Yes, Garland looks amazing but what about the rest of the themes included or the drupal.org site itself? The entire site is text heavy and looks out of date. Take the theme listing pages for instance: the screenshots are small, if there at all, and there's a whole list of cryptic links for resources, the issue queue and support material. This format might all works well for module development but the message sent to designers is that their contributions are second class citizens to modules and should follow the same conventions.
My example of the listing pages may not be THAT big of a deal but it is symptomatic of a larger bias within the project. Most people in Drupal would love for more designers to use the project but are rarely willing to bend to their wishes when they are contrary to development. Design is not a second class citizen!
So what needs to be done to get designers excited about the platform? Here's my shortlist to add to the comments above:
This comment has been much too long but reflects my own passion about the subject. The company that I work for, Image X Media, is design focused firm who uses Drupal exclusively for development. We want to see more designers using the platform because it will help Drupal improve and will ultimately help us by bringing a larger talent pool to hire from. Companies that do Drupal and design (Lullabot comes to mind) seem to do quite well for themselves. Let's get more of these people out there.
Rick
Design in sublime, UI is social
I have deviated from my design career a few years back because I was inspired by the community driven environments and new media model of many-to-many communications that were emerging. I felt that THIS needs to have it's foundation in society and replace the few-to-many model. It is an artifact of the transition that coders are dominating this environment right now. Designers in the past have been held in bondage by the choke-points of huge media conglomeration. The business model of big media more and more took the conversation out of 'we the people through freedom of press', and made design only skin deep. The functional half has manifested itself in the code development outside of that model, where now we are seeing the doorways to a healthy communications sphere with designers and coders on either side, each one holding an important enabler of the other.
THIS new environment is being populate by all the right building blocks by coders, and the designers know how to HELP arrange those building blocks into functional artistry. However, it is futile to try and design the "silver bullet" of UI design; that universal design that will enable anyone to navigate any information. The human element stripped by media conglomeration must be built again by local groups adhering to globally relevant and open frameworks.
I think the functional elements of menus and what information is navigable by those menus and links has to be a product of face-to-face conversation and collaboration. We can not mass produce this revolution.
Artistry will just happen more and more.
converting design
Seth,
A contest might work, might not. Eaton's done a great job with Gutenburg to show that Drupal can be themed to go with a wide variety of styles easily. Not having any knowledge of Moveable Type doing that sort of base theme would be difficult for me. I did once take the standard div output for cssZenGarden and implement it as a Drupal theme to see if it could be done (it can, was easy). However, the point of cssZenGarden is to serve as a learning center, not a theme skinning site so I never released it. (Also, many of those designs look great with static content, not so great with dynamic content)
In order to show folks that you do not need to be an uber php coder to port a theme design to Drupal, I wrote a quick and dirty how to port article to help get those interested get started. It's something I've been meaning to write for a while now.
The challenge has been dramatically increased for the entry level folks with the addition of JQuery as yet another thing to learn. This is not a bad thing, just another thing. To learn to use it in such a way as to supplement your sites design and not take away from it.
I think we've had more themes in Drupal 4.7 then in Drupal 4.5 or 4.6. Drupal 5.0 is even easier to theme. We'll get there yet.
-sp
I agree with you Steven,
I agree with you Steven, design isn't considered seriously important by many developers but with Drupal at least you have way more freedom than you do with most CMSes due to the wonderful theming system. As some have pointed out, it may seem steep to some designers but it doesn't require that much programming skill to get a theme to look the way you want.
I consider myself a usability person and a web designer. I am actually a student of cognitive science so usability is something I know very well, practically and theoretically. I regularly blog about usability on my own site too.
I previously worked with phpBB before starting to do Drupal themeing and development professionally, and I've released five free styles for it. I intend to port these to Drupal eventually, hoping to contribute a bit and bring in some spectacular rather than generic designs. In comparison to making styles for phpBB, Drupal is wonderful to work with, and I see its theme system as an asset rather than as a problem to themers, including newbies.
I've also, through my work with a Swedish startup that offers CMS hosting with Drupal, produced several themes, which can be seen here:
http://www.webbredaktoren.se/galleri
Maybe more creative themes that are easy to adapt would improve the general impression of Drupal as non-designer friendly. Regardless of the design, a good first step would be to develop a CSS framework by either taking an existing one like YUI Grids or the Zen theme, or write our own that is tailored for Drupal and which themes should be based so that we can provide theming tutorials at drupal.org that apply to all themes available at drupal.org, regardless of designer.
I am of the opinion that aesthetics and usability support each other when done well. I am not a programmer, can't produce code by the rate some people I've worked with can, and due to time constraints I am better at pointing out issues in core rather than fixing them. My opinion is that within the Drupal community development always takes precedence over design, and what is being looked for aren't designers and people who understand technology in use but programmers, who in my opinion, rarely possess a sense of usability. When people need theming done they ask for a coder, and this is a public misconception regarding what Drupal design work involves... all in all, the result is the theming always has to step down.
A good first step would be to approach design issues in Drupal from a conceptual point of view, take a usability expert's methods and actually put everything in context in a way that supports the needs of the users. A usability group could have VoIP meetings and work on producing wireframes for the developers. Such a group could help the different contributors work in concert with the usability aspects of the project (this includes more than just the UI). Drupal is already blessed with a powerful set of metaphors and abstractions to handle content but what needs to be done is creating a wider conceptual frame around it, a Drupal way of thinking that is consistent across all aspects of the project.
I'd like to help doing this and helping contributing new and better designs. In fact, it has been on my mind for a long time but I haven't had the time to do something about it.
I'll keep watching this blog post in case updates are made. This may be the first step to bringing good designs and good usability into Drupal for real.
About Garland
Great theme out of the box, the best I have seen, congrats Steven and the rest of the team.
But, when it comes to modifying it, I learned the hard way, its not simple at all, let me tell you, and I pride myself to know a little more CSS and HTML then the guy next to me, so we can't expect amateurs to be able to build themes ?! (I am not beaching, I am just pointing to the fact that someone trying to learn to create drupal themes would probably start from the default theme, and would find it very easy!)
Ideally I would like to see a theme with seperate css for the structure, a css for the colors and one for the typesetting so when one tries to change something he knows what part of drupal gets affected.
I also wanted to point to Matt's (don't know who else is behind it) Antinomia site which recently got itself a great theme, just so people know drupal can be very pretty if it wants to (by far the most stunning drupal site I've seen)
Default theme vs base theme
Garland is not meant as a base theme, but to look pretty out of the box. If you start from that, then you're digging yourself in a hole.
Generally, you don't want to start from a finished theme, as you first have to remove everything you don't like. There are better frameworks out there for Drupal (like Zen) that are just bare bones.
About Garland
G'day Steven... just curious to know what is happening with the gorgeous "Garland" theme you created? Particular, was wondering why it hasn't been released to the Wordpress community, outside of Wordpress.com?
I am aware of the some of the various "tensions" and issues that surrounded its release/availability on Wp.com, and I believe that it is part of the Drupal themes/template for members/users of Drupal... but I really like it, and have patiently, though frustratingingly, waited to see it as a release (Wp 2.1 compatible) either directly by yourself and/or associates, or via Wp.org service.
Thought I'd seek out some clarity from "Garland's" originator, rather than try to interpret others' perspectives or lack of.
Respectfully Yours, David, downunder
PS: any chance of a archive (contents) page/template, included?
Or if I really want a "garland" based web-presence, should I have to move to Drupal as my CMS?
Wordpress theme
I had nothing to do with the Wordpress port of Garland. The story behind that is explained in an earlier blog post.
In that thread, someone also points out that the WP version is available from a public SVN repository. That's all I know.
Theming is not Designing
As a creative director for a design firm with well-known academic and corporate clients, I've found Drupal quite promising and disappointing at the same time.
Yes, you can take a Garland/Zen-Garden-type approach to choosing alternate colors and fonts to the default template -- but that simply won't cut it for any serious publishing project. Our projects typically involve dozens on templates based on at least two or three entirely different style sheets.
We've experimented with a few approaches -- setting up code forks based on node type and view type, but this has taken a level of PHP wrangling that would terrify most designers. Perhaps we're just newbies, but we find that we have to go ridiculously deep into the code to get our sites to match the behaviors and information architecture that we've painstakingly built for our clients.
Sadly, we jumped on the Drupal bandwagon too late help with the Drupal 6 release. We have some great ides on how to design modules to make this more transparent for designers, but we certainly don't have the resources to implement them ourselves.
I don't think the Drupal design dialog has been going in the right direction -- we really don't need more theming tools, or clever ways of redoing the 3-column grid. Instead we desperately need some sort of way to make Drupal follow our object models, and our user interface, and transparently at that.
Otherwise, Drupal will just be glorified blogging software to the design community and miss its true potential.
Web design is a lot to tackle
The reason there aren't many great designers popping up in the community to lead the People is because most designers actually aren't very good at Web design, especially when it comes to sites that can be as big and complex as the ones Drupal powers.
Web design takes not only an aesthetic sense, but also an information-oriented sense. Semiotics meets semantics. One's approach must be holistic, not only designing a pretty theme, but perhaps sometimes designing the flow of interaction and information through the system. There are designers who can do this, mind you, but what you're looking for is a needle in a very large haystack.
As the complexity of what needs to be designed increases (the design of systems & information versus the design of a poster or a brochure), so does the necessary knowledge required to design it. This is why a lot of designers, especially casual or hobbyist designers, get confused by Web design or fail to address the real issues of it. There are a number of websites I would say are excellent examples of holistic web design, but they aren't exactly something for which one could easily whip up a Drupal theme... because themes are only a part of something bigger.
Drupal is organized complexity. It demands to be addressed holistically. It's elegant, however, and I am by no means claiming it could be "simpler." If it were any simpler it simply wouldn't be Drupal, but it takes a special kind of designer to design something that really makes sense of all of Drupal's organized complexity and I don't think it'll be easy to find that popping up in the community.
That said, I think Modulist's comment is spot-on and I wish I had read it before writing out most of thise comment. To get the kind of design the community craves, it's going to take more than your average designer and more than just a theme.
Well, it has been said
Well, it has been said before... but "designing a theme" isn't that simple at all... or is it?
To be honoust, the way drupal.org (or drupal.be) is designed, it isn't very easy to find things. Alsmost every subject is handeled only with text. It isn't only (for most non-geek users) a little (much) boring it also demotivates the ones who like to help, but simply can't because they don't know how.
Maybe it's time for make things easier, so more people can join the group of drupal designers...
And when I say easier I mean Easier (with capital letter ;-) ).
You really have to tell everything in a simple way. Even the program they have to use (like Inkscape or the Gimp,...) and the steps they have to take to make a design.
Look at Apple or ubuntu (mentioned before in the comments above).
Look at their designs, I 'm sure they played a great role in the succes of the OS.
Well, that's my point of view...
My unpopular rant
I'm fairly new to Drupal, but I've got a pretty extensive background in theme creation for those other open source CMS packages that Drupal users love to hate. There's no doubt in my mind that, under the hood, Drupal is superior to the likes of Joomla and Mambo. And I'm not so convinced that creating a professional theme in Drupal is significantly more complex than creating a professional theme for Joomla. But the perception among newcomers to Drupal or to the CMS world is that Joomla themes are simple and that Drupal themes are complex. This perception is reinforced by the existence of numerous high quality themes in the Joomla world and a paucity of high quality themes in the Drupal world. And I've got a few ideas about some of the reasons behind this mystery, so indulge me if you will.
The very existence of the myrid of themeing options available to Drupal theme designers is complex, confusing, and an indication of the repeated failure to create a workable system. The documentation on Drupal.org and other sites is an absolute mess of intermixed PHPTemplate, XTemplate, Plain PHP theme, and Smarty documentation, not to mention the numerous scattered references to the different requirements between 4.5, 4.6, 4.7, 5.x, and 6.x versions. It's no wonder that the very few high quality themes available were created by the folks who actually played an active role in creating the system. The documentation is absolutely unapproachable for someone new to the system.
There's an amazingly silly perception amongst a vocal group of Drupal advocates that complete, professional looking themes are unnecessary because every user is going to create their own look from scratch using their own custom CSS and PHP code. Nothing could be further from the truth. Such complete overhauls of a theme are limited to a fairly small number of professionals who make a living as web site designers. Most of the people who would benifit from the use of an open source CMS package are those who would like most of this work done for them in as professional a manner as possible. I'm talking about small business owners, little league coaches, non-profit organization volunteers, and the like. These people don't want to completely overhaul a base theme. They want to replace the standard logo with their own logo, change a few bits of text, add their content, and have a great looking site. Hundreds of technically savy users might appreciate the flexible complexity of Drupal's theme engine, but tens of thousands of not-so-savy users seem to appreciate the not-so-complex solutions offered by commercial Joomla theme vendors.
Joomla benifits greatly from the inclusion of demo content in a standard installation. When a user installs Joomla for the first time, the front page looks like a real website, even though this demo content will eventually be replaced. There is no need for a new user to 'imagine' what a completed site might look like. First time Joomla users will typically install and test various templates using this demo content before they ever even create any content of their own. By comparison, a new Drupal installation looks sparse and incomplete. A user might test different templates before creating content, but it is difficult for many users to envision how the template will impact a website that has a full body of content unless they actually take the time to first create that content.
By embracing the commercial component vendors, Joomla has created a cottage industry that is extremely appealing to the not-so-savy masses. There is a seeming smorgasboard of choices available to Joomla users for tasks as specialized as interfacing to Google Maps. And for more common needs such as comments and user forums, the options seem endless. I'm all for open source solutions, but it's obvious that the market wants quality choices and they're willing to pay for them.
Finally, there is an arrogant denial amongst many Drupal advocates that problems even exist. When a reasonable argument is presented that the Joomla world is ripe with hundreds of professional templates that look great out-of-the-box, such arguments are often met by unrelated attacks on obvious weaknesses in Joomla. Such attacks not only miss the point regarding template quality and usability, but they alienate many of the users who see the obvious weaknesses that I've outlined.
It doesn't help matters much when the militant Drupal advocates insist that iTheme and BlueMarine are equal or superior to the better commercial Joomla templates. Take a look at the latest offerings on the demo pages at rockettheme.com. If you really believe that there are templates in the Drupal world that approach these products in quality, then I would suggest that you are part of the problem.
As I stated at the beginning, I find Drupal to be FAR superior to Joomla in nearly every significant way. Just like Betamax was FAR superior to VHS. So spare me the ivory tower speeches. This community has to address these issues or it will loose out to an inferior technology.
My two cents.
How Do Designers Get Involved?
I suppose a burning question is - how does one get involved?
I'll confess to being a WordPress addict for a while, but I'm slowly learning the joys of Drupal. Having created a few themes for WordPress, I'd be interested in turning my hand to Drupal and perhaps mucking in with the community to make things prettier.
If you've any ideas, drop me a line.....
The one thing that made me a "scared away designer"
* It wasn't negative design comments by coders (I didn't even get that far into the forums).
* It wasn't fear of trying to theme such a powerful and flexible CMS.
* It wasn't that I don't get web basics like CSS, xml, html, heck, even php.
It was this and this alone:
Attempts at finding clear directions to turn my beautiful Gimpshop design into a workable Drupal theme left me with... NOTHING.
* I scoured for video tutorials that went beyond changing the colour in Garland.
* I dug through files in pre existing templates. (This is how in one sitting I taught myself to make a semi-fluid Joomla theme from photoshop knowing no more than basic HTML and a little PHP.)
* I attempted searching Drupal which seems to insist on lumping every module, forum post, article, blog entry, kitchen sink etc into one place.
* I googled until I was barely able to blink anymore.
I'm sure that like "The Truth", "The Answer" is out there somewhere. As a reasonably tech happy designer, all I ask is easily findable, clear, step by step instructions as to how to take a bunch of CSS and images and make it Drupal happy.
New CalArts site runs Drupal...
http://www.calarts.edu
Hey people, I just wanted to twig you all on, especially since Calarts was mentioned in the comment thread for this post, that we've just finished a new site for the California Institute of the Arts (CalArts) at the above URL.
The site's running on Drupal 5.x and I think perfectly exhibits the infinite aesthetic possibilities that Drupal can afford designers/developers... on this project we really thought about bridging aesthetic flexibility with overall sustainable site scalability - which meant using 3rd party modules rather than jumping into core code etc.
Read a Case Study of the project:
http://www.designguru.org/projects/nonprofit--educational/california-ins...
Cheers,
Qasim