Milestones

Staging complete on drupal-dev.l.o.e  - May 2

Testing/edits - May 9

Migration to production - May 16

Training for "front-page editors" - May 23 

"Live" (URL redirection) - May 26 

Background details

Currently we have 4 home page views: General/Undergraduate, Graduate, Faculty, Ecampus.
The goal is to move these 4 views into Drupal.  Guin and Cascades views will be added next.

Views
Currently, users select a view which is then held in a cookie.  This would continue to be the case for unauthenticated users.
Users who authenticate are assigned a role based on view.

Roles
Roles would match views: General, Graduate, Faculty, Ecampus
Eventually we will need an Undergraduate role.
There will need to be Front Page Editor roles exclusive to each different views/groups.  For example, a Front Page Editor for the Graduate group, a Front Page editor for Ecampus, etc.
I think we will need to talk about how this happens, what modules and so on, because I've read about the different modules used to control access, but haven't tried them out and am a little unclear on this.

Content 

1. Menus
    Ecampus has a different menu than the others.  This is currently tracked by the view cookie.  If authenticated and belonging to Ecampus role,

2. Central area
    The central content space is broken into 4 chunks.  The content for each of these chunks needs to be able to be independently controlled for each view.
    Currently, the chunks that need to be available are:

• Did you know (text and photo)
• Featured (text and photo)
• Staff Picks (librarything widget)
• Ecampus ICAP list
• Blank Filtered HTML textbox for page editors to add links and content as needed. For example, Ecampus "Accessing Materials" links

3.  Quicklinks
    Top, left chunk.  Since authentication will be controlled by LDAP, anyone with an ONID should be able to log in and customize their Quicklinks. Once Quicklinks have been customized, changing views should not override custom links.  I'd like to see an easy method for users to do this.  An "Add Quicklink" link right under the list of quicklinks or something like that, rather than switching to an admin menu in the left.

4. Right hand column
    Content needs to be changed for each view.  I don't think we will need to allow users to change this section.  We can set it up for them since it should need to change frequently.

• Chat widgets (Valley, Ecampus, and eventually Cascades)
• News from OSU Libraries News content type (previously shown in the news scroller bar) 
• Giving link

• Blank Filtered HTML textbox for page editors to add links and content as needed. For example, Ecampus "Getting Help"

Design changes

As mentioned the news scroller should go away, with a static list of news titles shown in the right hand column for all views.

Change Your View needs to be removed from the menu.  This will be an audience bar across the top under the green header, similar to OSU's home page.  Since this is Renee's original design, I will ask her to do a mockup styling the new audience bar and News section for us.

Drupal's method of adding inline javascript will be implemented to improve pageload performance.

Chat boxes will be changed from embeded meebo script, to images with custom javascript (I'll send an example later)