An Editor's Perspective on Creating Content in Drupal
So I'm not a Drupal expert, and I don't play one on TV. What I do do is use Drupal everyday, using Urban Insight's flagship site, Planetizen. I'm a perfect test audience for Drupal usability, because I can give a detailed perspective from a user standpoint.
Right now, we're deep into upgrading Planetizen from Drupal 5 to Drupal 7. In the process, I've gotten to take advantage of the highly talented UI team in a way that I haven't previously. We're rebuilding the site from the ground up, and it has given me a chance to pull from years of experience to develop new ways to efficiently enter and present content.
Here is a grab bag of tips that have out of the rebuild so far:
1. Content is getting more and more visual. I skim hundreds of news stories every day, and an image of any sort, whether it be a picture of the author, a photo of the location/topic in question, or even just an icon representing that topic area, visuals are now essential. Rather than just decoration, I believe they orient your brain as you surf the web to locate content more efficiently and accurately.
2. Simplify your user permissions: It's tempting to look at user roles as a list of things that person (Editor, e.g.) needs to be able to do. But we realized its much more efficient and simple to think of user roles as a number of hats that a person could wear. So rather than laboriously assigning all permissions to the Editor, the Editor also gets the basic functions assigned to the authenticated user, the writer, etc.
3. Put a SUBMIT button at the top of all of your content types: I post 10 stories a day to our news site, and I can't tell you how much scrolling I've had to do over the years because the PREVIEW and SUBMIT buttons were only on the bottom of the form. This is one of those things you wouldn't think of if you weren't coming from my perspective.
4. Content types are becoming less relevant: It's not what type of content you are posting, but how popular and relevant it is. We realized that with all of our content types - original features, aggregated news, blog posts, etc. - it doesn't matter what type of story it is, but how popular and interesting it is. Our slideshow is currently just for original feature content, but in Drupal 7 we're going to assign any content to the slideshow that we think is most exciting to our audience. That's what people are looking for, not whether the person wrote for me or for a blog or the Honolulu Star-Advertiser.
Overall, I'm very excited about our leap into Drupal 7 and I'm greatly looking forward to finding more innovative ways to use it to present high-quality content to our audience.
7 comments
A very useful article, much
A very useful article, much needed input in the community, thanks for sharing, and keep them coming please!
Until I read this...
...I had never thought about #3. It just never occurred to me to put the preview and submit buttons at the top. But it makes total sense considering that all the settings at the bottom can generally be left to their defaults on a production site.
Thank you for this perspective
We want to continue improving things for site editors, content managers, those who work within Drupal daily *after* a site is built, deployed etc.
To do so, we need to hear experiences and lessons learned like these. Thanks. I'm posting a link to this article in http://groups.drupal.org/node/143274 (Exploring web manager & content editor topics)
Re: #3
It has been solved with Admin + Rubik theme both in D6 and D7, see example: http://skitch.com/omega8cc/f4sku/fullscreen
Hi Tim,
Hi Tim,
I am the maintainer of http://drupal.org/project/content_type_extras. I have been going back and forth for a little while about adding the submit button to the top of the content type edit pages. I have had a couple of instances where it would have been useful, but I figured it was more of a unique situation. Having read tip #3 though, I think that it may be more useful for people than I realized. I guess I'll quit going back and forth and get it added!
Thanks!
The Good vs. the Bad
Problem is that while that might be good for content Publishers, it is bad for content Creators who typically need to be guided through the content edit form.
For example: if you are using any SEO tools (e.g., NodeWords, PageTitle modules) where the content editors need to manually input text, they'll get lazy with the submit button so conveniently located at the top.
Or, they'll skip other important content creation steps below Body field.
Ideally, would be nice to customize the content edit form template based on role. I have never had this need arise, but as a Site Builder, my curiousity is now piqued.
Tyme
Some good points
I'm primarily a developer/trainer, but I've done a fair amount of content creation in Drupal as well. And I agree that having the Save, Preview and Delete buttons on top of the page would be a huge help.
Content types are important for Views, and are necessary if different types require different fields. Otherwise agree with you there also.
Post new comment