Archive of: drupal
Leisa Reichelt reflects on what Mark Boulton and herself learnt during the D7UX project this summer, and puts her finger on a big issue facing the Drupal community going forward: who is the target audience?
And so we have this tension. Drupal as a ‘Consumer Product’ and Drupal as a ‘Developer Framework’. Currently, the official direction is that the project is going to attempt to be both. I think this is a serious problem.
The target audiences for each of these objectives are so far removed from each other in terms of their tasks & goals, their capabilities, their vocabulary, their priorities. An attempt to devise an interface to suit both will result in an outcome that I expect we’ll see in the release of Drupal 7 – that is a compromise to both parties.
From a fantastic piece by Christopher Calicott looking at how front end design and development is treated within the Drupal community.
Having such high standards for writing PHP code while playing so fast and loose with front end code and treating it as though it’s a non-issue, even while the rest of the world does it this way, is not only a gross double standard within the Drupal community, it is currently beginning to get the attention of the Web world outside of Drupal — and not in a good way. We’re positioned in the press to take off like a rocket and gain real longevity, and yet in the web design community – people who talk around the world at conferences, on podcasts, et cetera – are starting to hear that Drupal, despite the good things about the code they’ve heard, makes minced meat of their beautifully executed, semantic XHTML, and there are no plans within the leadership of the Drupal community (yet) to raise the standard for front-end code to the same degree that they have on the backend.
Firstly, developers take writing code very seriously and have stringent – but ultimately plain and simple – coding style rules to follow with their module development. Designers have the same sorts of practices. It’s what they do and it’s equally as important. It is time that that is fully recognized in the Drupal community and an effort be made to bring this paradigm (elsewhere largely already in practice) into our community. Designers feel just as strongly about a developer playing fast and loose with improperly written, unsemantic XHTML as developers do about designers who make dumb mistakes with PHP or try to talk shop when they are out of their depth. In fact, dare I say it – if you’re writing poor, unsemantic XHTML markup, it’s due to your lack of understanding of what you are doing, at this point. Web standards are widely adopted in the Web world. Drupal ignores this fact at its peril.
It’s an issue that’s been bubbling under for a while, and this is the best treatise I’ve seen on it yet. Required reading for anyone involved with Drupal on any level.
The internet is one big machine.
- We started by linking machines
- Then we started linking pages
- Now we’re linking data
- Next linking things (like your fridge)
Finally got round to updating to Drupal 5.1. I’ve done some pretty thorough testing and it all looks good, but if you notice anything strange please leave me a comment (which are no longer moderated, thanks to the new captcha, we’ll see how long that lasts).
Now that I’m up to date expect to see some changes in the near future. There’s a new theme in the works and some toys that I’ve been wanting to roll out, but could only do on 5.x
Caveat: The appearance of said theme and toys depends wholly on how much free time I have in the next few months.
Thank you to Google for the unbelievably generous support. This represents $100,000 worth of financial contributions to Drupal development, $10,000 of which will be donated to the Drupal Association.
A few of the projects that will be worth keeping an eye on are the Jabber/XMPP integration, RSS/Atom improvements, an SMS framework, and an automated staging environment toolkit.
You know you’re getting somewhere in the world when you get your own song.