Campus Web Steering Committee (CWSC)

1. Campus Web Steering Committee (CWSC) March 8, 2010

2. Agenda Discussion Item: Campus Website Refresh • Reasons for refresh • Statistics • Review of other university sites • Wireframes of possible designs for the home page portion of the refreshed Website Information Item: Update on Mobile Framework • Brett Pollak (10 minutes)

3. Brett Pollak Campus Website refresh

4. Why refresh the campus site? • Optimize the use of space • Header • Layout of page elements • Links to audience-based websites

6. Why refresh the campus site? • Optimize the use of space • Header • Layout of page elements • Links to audience-based websites • Evolve the design to fit with campus-wide templates both aesthetically and technically • Leverage the common Cascading Stylesheets (CSS) • Sets the stage for continuous improvement

7. Campus-wide Templates Websites inside and outside the CMS are using the templates Over 40 sites now in CMS Another 30 using the templates outside the CMS. The home page should tie in with this design

8. Why refresh the campus site? • Optimize the use of space • Header • Layout of page elements • Links to audience-based websites • Evolve the design to fit with campus-wide templates both aesthetically and technically • Leverage the common Cascading Stylesheets (CSS) • Sets the stage for continuous improvement • Allow for flexibility to feature things on the home page that may change monthly/quarterly, • Current initiatives, social media, frequently accessed pages, etc.

9. Refresh Guidelines • Refresh would be a design refresh not a content and information architecture change • Generally keep the same elements in roughly the same location • Minimize any impact to UCPA for updating home page • Refresh would include • Home page • Explore/Learn/Apply content • Search and People Directory decorators • (News sites)

10. Stats • Home page is viewed on average over 30,000 times per day. • That’s once every 2.8 seconds during a 24 hour period. • 30% of students surveyed said the campus website had at least “somewhat of an influence” in them selecting their college.* * US News & World Report

11. Last campus site refresh

12. Who are out main audiences? • Prospective Student related content has the most aggregate page views under ucsd.edu • About Undergrad College System • Departments and Programs • Admissions • Costs of Attendance • Application • Financial Aid • Current Students • Makes up about 30% of top 100 most-viewed pages under ucsd.edu

13. Top pages under ucsd.edu

14. Reference sites • Middle banner for audience site links • http://gvsu.edu/ • http://www.virginia.edu/ • Side banner for audience site links • http://www.smsu.edu/ • http://www.fhu.edu/

15. Reference sites • Functional Footer as a content area and for social media links: • http://www.wfu.edu/ • http://www.fhu.edu/ • http://www.unr.edu/ • http://www.fiu.edu/ • http://www.ucr.edu/

16. Reference sites • Nice use of right-side callout for features • http://www.hagerstowncc.edu/ • Similar to our news content structure and nice use of space for news and features • http://www.uchicago.edu/ • Nice use of color • http://www.vt.edu/

17. Wireframe options Option 1 • Thinner header • Functional footer • Moved Academic Units up higher Option 2 • Thinner header • Functional footer • Moves audience links below feature area • Shows Events above Academic Units Option 3 • Thinner header • Functional footer • Moves audience links to the side • Shows Academic Units and E/L/A higher on the page • Moves Athletics, Preuss and Med Center into E/L/A • Features Giving to UCSD

18. 2 Year CWO Roadmap Key: Complete In Process Proposed Ongoing 2010 2011 UXT Project Design Requests Migrate Websites to the CMS Blink Operations UXT UI Framework Support Portal Services Transition UCPA Maintenance/Support TritonLink & Current Students Redesign Financial Apps UI TL Phase 1 Giving Website Redesign Online Giving UI Mobile framework Apply mobile framework to Student & Other Apps Online Giving Redesign Phase 1 & 2 Maplink Upgrades (Security)Timekeeping Roles Screens Lightweight Event Form Framework Prospective Students/Admissions Redesign Search Enhancements Campus Website, Search, and People Directory Refresh Rollout New CMS templates CMS Sites Model CMS upgrade Move RMP into Blink

19. Next steps • Finalize wireframe for home page • Wireframe for supporting pages and systems • UI Designs • HTML/CSS coding • CMS templates • Content Migration • Decorators applied to apps. • Deployment

20. Brett Pollak Mobile framework update

21. Involved 8 Campus IT Groups ACT, ACMS, SA, Colleges, Libraries, SIO, Bio Sciences ACT Student Affairs Libraries

22. Selection Criteria • Sustainable over a 1-2 year period of time. • Include open source or industry standards. • Support various mobile devices. • Require little training for development. • Easy to migrate off of or work with new technologies as they become available.

23. Reviewed 8 Mobile Frameworks UCLA, MIT, SproutCore, PhoneGap, jQuery, WebApp.NET, Sencha, iMobileU

24. Recommendation • UCLA Mobile framework • Standards-based lightweight mobile framework • Device agnostic • Apps can leverage the framework regardless of whether they are built in JAVA, .NET, PHP, etc. • The framework handles the device-by-device planning and implementation, not the developer! • Campus apps can leverage the framework without being co-located on the same server

25. Implementation ACT hosts the framework, everyone else plugs in.

26. UC-Wide Adoption • UCLA launched mobile site in Fall 2010. • ITLC adopting framework UC-wide • UC Berkeley to launch mobile presence based on UCLA framework in Spring 2011. • UC Riverside and UC Davis are also in process • UCSF also signed on.

27. Next Steps • Launch new m.ucsd.edu (~April) • Launch Apps that point to m.ucsd.edu functionality • iPhone/iPad • Blackberry • Android • Add new functionality • Integration with the CMS Web content • SSO Integration • MyTritonLink