Tag: content management systems
After navigating the waters of not one, but 3 different CMSes for the same set of websites, Guay shares her insights into what works, what doesn’t, what’s great and what’s just plain dumb about Drupal, Plone and WordPress. She’ll even talk about her experiences making all 3 share the same sandbox and not fight (too much) over the toys.
When Mount Holyoke College first moved its main website into Drupal, the goal was quick migration, not smart implementation, and the school did some decidedly un-Drupalish things. Two years down the road, the team used a major redesign as the opportunity to start figuring out how to make better use of its platform of choice. The catch was the team needed to upgrade in place rather than start over. In this talk, Proctor will share some lessons learned from the process of replacing the wings while the plane is in the air.
Learn how user experience testing can save your university money, reputation and headaches. This session will cover the University of Minnesota’s efforts to incorporate user feedback into the software purchasing process. The session will cover several use cases that illustrate the considerations and challenges faced by teams at UMN making major software investments, and will show how user feedback helped those teams make data-driven decisions, avoid choosing the wrong tool, and prepare for the tools’ rough edges ahead of rollout. You wouldn’t dream of buying a car without taking a few options for a test drive. Why would you spend what could be millions of dollars on a software solution for your campus without taking the opportunity to test it?
Multi-headed Drupal (DPA9)
A common challenge for large universities is IT's desire to have a single, centrally-managed web presence while academic departments want to maintain their own individuality, both from a design and management perspective. That leads to an inevitable tug-of-war between "one big site" and "lots of little sites". One of the strengths of the Drupal CMS platform is that it has several tools for managing "companion sites". Those could be entirely separate sites with some commonalities or one "site" that appears as distinct sites to visitors. Each approach has its own set of benefits and trade-offs. This session will explore several leading ways to build and manage a multi-headed Drupal installation, including Domain Access, Organic Groups, and Multi-site, including examples of organizations that have done so. It will also ask the question of whether a multi-headed Drupal is necessary in the first place; often it is not. Attendees should come away better-armed to evaluate how, and if, to roll out Drupal for a multi-part site at their institution.
Authors Are People, Too (UAD10)
If content is king and user experience is crucial, what can we say about the experiences of people who author content? What makes a good authoring experience, why should I care, and how can I improve my authors’ experience with the CMS? The fundamental purpose of a CMS is to empower us to create and manage Web content. Good user experience should start with the people who are responsible for using this system to work with content. If the process for authoring and editing content in the CMS is cumbersome, authors won’t be actively engaged in maintaining it, and our sites will be woefully out-of-date. Good authoring experience (AX) will make the CMS easier to learn and easier to use, increasing the likelihood that authors will take a more active role in creating content. Active authors do not require excessive post-training support and keep content up-to-date. CMSs should be tailored to their authors, not the other way around. This session will provide experiences and lessons learned as Penn State has iteratively improved our CMS authoring environment to empower its authors.