18
Presentation Layer: The CMS as a Manager OHECC 12 May 2010

Managing Multile Interfaces with dotCMS

Embed Size (px)

DESCRIPTION

U of Akron has aggregated the management of multiple interfaces behind one system - dotCMS. This presentation outlines some of the benefits and cost savings of resisting "software bloat".

Citation preview

Page 1: Managing Multile Interfaces with dotCMS

Presentation Layer:The CMS as a Manager

OHECC12 May 2010

Page 2: Managing Multile Interfaces with dotCMS

Today

Just what do we mean by the “Presentation Layer: The CMS as a Manager”?

Presentation Layer in ActionZiplineHR Employment AppCampus-wide LCD Monitors

What allowed dotCMS to play in this expanded role?

How this benefits UAkron

Page 3: Managing Multile Interfaces with dotCMS

Intros

Eric Kreider– Director, Web Services– Central Support

• Programming• Training• Distributed Content Management

Bill Beardslee– SVP, Strategy and Development

Page 4: Managing Multile Interfaces with dotCMS

The Issue: Software Bloat

“Stop buying new software every time you create a new interface”

Page 5: Managing Multile Interfaces with dotCMS

Presentation Layer: The CMS as the Manager

Page 6: Managing Multile Interfaces with dotCMS

dotCMS and AkronBe

gin

CMS

Impl

emen

tatio

n

Trai

ning

Empl

oyee

Intra

net

Ziplin

e In

tegr

ation

LCD P

roje

ct

Laun

ch N

ew S

ite

HR E

mpl

App

l

2008

2009

2010

2011

Page 7: Managing Multile Interfaces with dotCMS

dotCMS

Enterprise Grade CMS– Java, Open Source - J2EE/Oracle Stack– CMIS - Structured content– Internationalization - Multi-site/Multi-tenant

“Look Ma, no Java developers!”

Data-driven sites integrated with other apps can be deployed by Web DevelopersSkill Set = HTML, CSS, Velocity Greater utilization of a more commonly found resource

Page 8: Managing Multile Interfaces with dotCMS

What Enables dotCMS as a Manager?

Standards

FeedsPlug In Arch

SSO

Page 9: Managing Multile Interfaces with dotCMS

CMS as a Manager - Zipline

ZipLine - employee and student self-service portal Oracle / Peoplesoft

ZipLine - pulls data from dotCMS The Buzz - news stories to homepage, XSLT pull from dotCMS Calendar - XML registered to portal via native portal

registration service News - RSS feed registered through native portal registration

service

Page 10: Managing Multile Interfaces with dotCMS

Demo Zipline

Page 11: Managing Multile Interfaces with dotCMS

CMS as a Manager – HR Empl App

Automate application process Jobs already in the dotCMS mySQL DB and searchable

Job applicant doesn't need to specify WHICH position Attachment automatically attached to position application Application and attachments automatically transmitted to search

committee Reporting for HR Indication of suitable candidates Ethnicity reports

Page 12: Managing Multile Interfaces with dotCMS

Demo HR Empl App

Page 13: Managing Multile Interfaces with dotCMS

CMS as a Manager - LCDs

New initiative to place LCDs throughout campus Distributed in regionalized content zones Company has interface which would require new IDs, training

WebTeam built interface with push to interface allowing input with standard dotCMS editing interface

Consolidate login Consolidate training Distributed content management via dotCMS processes already

in place

Page 14: Managing Multile Interfaces with dotCMS

Show Mock Up of LCD

Page 15: Managing Multile Interfaces with dotCMS

CMS as a Manager – Emergency Response

Main Points of Outbound Messaging Consolidated CMS acts as UAkron’s Bullhorn

Communications Director has full command Low Grade Emergency (Snow Closure)

Owns a portion of the homepageHigh Grade Emergency (Natural Disaster)

Can opt for simple Homepage and publish onStudent HomepageWWW HomepageZipline

Page 16: Managing Multile Interfaces with dotCMS

UAkron capabilities power dotCMS

Graphic DesignerHTML RSSDreamweaver TemplatingPhotoshopIllustrator

2 Senior Developers PhpmySQLLDAPSys Admin experienceSome XML exposure

Page 17: Managing Multile Interfaces with dotCMS

Where does this get UAkron?

• Greater utilization of a single investment

• Centralization of templates for branding

• Centralization of training– Train once on CMS; post content on WWW, portal, LCD, “Next”

• Significant adoption across the University– 300+ users

• Greater consistency of message across multiple audiences, medium

• All done with Web Developer resources