ARHU Drupal Presentation 2/3

Post on 23-Dec-2014

800 views 2 download

Tags:

description

A case study of the ARHU Website done in Drupal and launched in September, 2009. Presented by Megan Weng, IT Coordinator for the College of Arts and Humanities, University of Maryland.

Transcript of ARHU Drupal Presentation 2/3

An Inside Look at the New ARHU College Web Site

Megan WengFebruary 3, 2010

1

This talk is for

Detailed technical discussions of Drupal

2

• Discussing the process of building the ARHU website with Drupal

• An overview of the features and how they are supported by Drupal

• Strengths and challenges of Drupal solution

Not for

A Brief HistoryLaunched on September, 2009

Took a year from requirement to 1st launch

Totally built in house through a Drupal pilot project with OIT and hosted by OIT

3

Basic Facts of ARHU Site In Drupal 6.9 ~190 pages including all external links Supports ~15 users Uses 30+ modules Three menu systems

Primary Menu, Main Menu, and top Menu Basic features

In-context editing LDAP integrated Google Analytics enabled Forms with Captcha Password Protected pages Fellowship/Employment/News/Events Database and more…

Continues to evolve

4

Basic Facts of ARHU Site

5

Project PhaseThe Project From Start to Finish

Requirements PhaseDesign PhaseImplementation

6

Requirements Phase (I)Problems in the existing site Difficult to navigate/find information Difficult to maintain/outdated information Outdated design & technology (site designed 10 years ago)

Criteria for the new site Easy to navigate Easy to maintain

Restrict access rights Consistent look & feel

Solution: Content Management System!!!

7

Requirements Phase (II) Primary Goals

For perspective students to apply to ARHU

For current students to obtain information on resources

For current students to communicate with other students

For alumni & friends to donate to ARHU

For alumni to connect with ARUH and other alumni

For staff/faculty to obtain information on resources & research

For inter-department communications

 

8

Requirements Phase (III)Primary Audience

Current Students

Perspective Students

Faculty

Staff: Department Chairs, Dean’s Administrations

Alumni

Donors

General Public

9

Requirements Phase (IV)Review of existing web site

Review of peer institutions web site

Discussions with stakeholders

The Result: Web Site Architecture

10

Web Site Architecture

11

Design Phase Design mock ups produced based on information architecture and

presented to stakeholders for feedbacks

12

Before After

CMS EvaluationOpen Source vs Commercial ProductsPlatforms considerationEvaluation

DrupalJoomlaPloneezpublish

13

Implementation (I)Theme Development

used zen theme as starting point heavy CSS styling (FireBug!!!) Major browsers support was a big

challenge heavy usage of Block to control layout

Navigation: menu systems Nice Menu module

Define Content Types CCK module Examples: Event, News, Fellowship, Job

14

Implementation (II)Development Process

Before First Release in 9/2009

15

– After First Release

Features (I) In-context editing

Administration menu module

LDAP Integrated LDAP module

WYSIWYG editors FCKeditor module IMCS module files

uploading – images, pdf, doc

Home Page Views module Panels module: multiple

views on one page Dynamic Display Block

module: slide show16

Features (II)Fellowship DatabaseEmployment DatabaseNews & Events

DatabaseCCK moduleViews module

17

Features (III)Google Analytic

EnabledGoogle Analytic module

Password Protected pagesProtected Node module

Online forms with Spam controlWebform modulereCAPTCHA module

18

Features (IV)These features will be incorporated into the next

Drupal upgrade

WorkflowRules

Granular PrivilegesTaxonomy?

Multi-sitediagram next slide

19

20

Challenges/Limitations/ComplaintsPerformance issue!

Turn on Drupal optimization: Site Configuration -> Performance

Opcode caching on PHP

Some features are supported multiple ways, while some features are not fully developed Image gallery Workflow

Theme development can be very challenging CSS styling can be painful! Heavy CSS styling causes side

effects

Migration between environments is a pain!

21

Strengths of Drupal SolutionVery easy to learn/use for the users

Very flexible

Lots of modules offering lots of features

Large community of user base

Powerful social networking features

22

Next StepsContinue to improve the design and user experience

Improving performance

Utilize the social networking/media features of DrupalBlogging, forums, RSS, audio/video

Providing consistent themes/templates for departments

Applications development within Drupal or without Drupal?

Keep an eye on Drupal 7…

23

Q & AIf you like to hear a talk on a particular

feature discussed today, please let me know!

24