
This post continues our mini-series on web strategies for Higher Education and Drupal. Last time, I reviewed 7 Suggestions for New Drupal Users in Higher Education, so this time I have 11 smaller scale improvements that Drupal users in higher education can deploy to get even more from their sites.
Use themes to enforce uniform content presentation: By spending a little extra time with your theme you can ensure that the presentation of your site is uniform and consistent across all pages, and that the design is completely separate from the content. With these controls in place, your site will look better and content will be easier to edit for your users.
Use Views to construct queues: If you use the Workflow Module to track the process of content before publication, you can use the Views module to construct lists of posts for your editors and reviewers. We often think of views for constructing lists of content for the forward-facing parts of a web-site, but it's also useful for the internal parts of your site.
Develop administration and publishing policies: It's much easier to encourage your users to contribute to the project of maintaining your website if you develop a clear set of organized guidelines. Also, because big Drupal sites can be so customized, keeping a written collection of how things should work will save future headache.
Provide Feedback tools to your Users: Because University websites serve such a central role in disseminating important information, users often have strong feelings about the design, user interface and presentation of information on these websites. Make it easy for your users to provide feedback with contact forms and then pay attention to what they say.
Let users personalize profiles: Some basic social networking-like functionality can help users connect on your site, and provide users with more associative ways to connect with each other. Drupal provides user profiles, so this is a matter of exposing profiles, adding functionality, and allowing users to do the rest.
Use SMS to keep users current with your site: We think of Drupal as a system for powering websites but Drupal's power and capability extends beyond the web. You can use Drupal's SMS integration to keep users up to date with changes on the site or pending administrative requests.
Integrate with Facebook and Twitter: It's possible to integrate Drupal sites with external social networking tools such as Facebook, Twitter, and Ning. If your campus uses any of these tools, you might benefit from integrating your Drupal site with these other websites.
Use rich text editors to make editing even easier: Drupal supports editors like FCKeditor and TinyMCE, which make the process of editing content for non-technical users much more simple.
Use Panels for complex layouts: The Panels Module in Drupal allows you to set up and manage complex layouts without a lot of fuss, or highly specialized background. If you have pages that need to pull information from a diverse collection of sub-sites, Panels might be just the thing you need.
Improve and standardize navigation: Large and complex websites need coherent systems to ensure that all of the contort is accessible and usable. The more regularized your navigation tools are, the easier your users will be able to find what they're looking for and the better they'll feel about the site.
Delegate as much website management work as possible: With access control schemes, workflow queues, and coherent administrative policies in place, web developers can delegate much of the administrative responsibility to other users, and spend their time developing new features and functionality for the website.
3 Comments
Note number 2 on using Views
Note number 2 on using Views for administrative views is excellent; on three different sites, I've set up an internal queue of unpublished stories and other content types that can only be accessed by certain users, in order to keep the content moderated by a select few. I think most Drupal users have barely scratched the surface when it comes to the power within Views!
I totally agree, and for the
I totally agree, and for the record, we use one of these internal-queues for trellon.com, and as the wrangler for the blog, I find this to be a great improvement, as it centralizes the process and workflow, and doesn't require us to use multiple systems to manage everything. Every system has it's strength, and I suspect that there are *probably* better ways to solve this (and other similar problems) but having everything in one place is worth a lot more, than a piddly feature here or there. It's not always the case, but for website content, it's true.
I think the reason that views is under-utilized relative to it's ability has to do with the fact that views--at it's core--solves a very user-interface/user experience problem, rather than a programing/development/feature problem. That is, building complex queries for content isn't ground breaking or even that hard to do with a text editor and a bit of background in SQL. It is hard to do casually, and by opening SQL up to *everyone*, basically, you get all manner of power and ability. Which is really cool, almost too cool to be able to cope with properly. The issue at the moment is figuring out how to use that power, and figuring out how to use that power for good, and what kinds of problems this new power lets us solve.
It's ironic, but comforting to folks like me, that the "next hurdle" isn't how to make the technology function, but rather how to use the technology so that it makes the sites as productive and useful as they can be.
It's been my experience that
It's been my experience that the two wysiwyg editors listed are buggy and unreliable. I don't feel that I can fully support the statement that drupal makes it easier for users to create rich text content. I would love the communities feedback on this.
I love the idea of SMS integration. The possibilities for its use are very exciting! Also thank you for the information on panels. I don't fully understand it's use from your description but will check it out.
Post new comment