2. 2
Snapshot
OASIS Web Services
• College of Arts & Sciences
• Content management web
solutions to departments,
centers, and programs
• Free of charge to College
• 70+ departments
ITS Web Services
• Office of CIO, ITS
• Web design, development, and
content management services for
ITS, campus units
• Cost recovery model
• Serve internal and external
customers
3. 3
Issue: An Inefficient Model
Landscape
• Different technologies
• Duplication of efforts
• Lack of standards,
policies, processes
• Resource constraints
• Customer confusion
• Inconsistent UX and
branding
4. 4
“Create, administer, and support a truly collaborative
approach to delivering web-based services to UNC-
Chapel Hill and beyond.”
Proposal
5. 5
OASIS & ITS Web Teams Unite
First Step: A Partnership
10. 10
Benefits
• Building knowledge via cross-
disciplinary skills, insights, and
perspectives
• Communications (i.e – Alert
Carolina messaging)
• Standards
• Design and branding
consistencies (set of WP themes
for different use cases)
• Increased efficiencies, reduced
costs
• Meeting wider range of needs
• Scalable infrastructure
• Security (i.e – plugin and theme
review process)
• “Future-proofing”
“If you want to go fast, go alone. If you want to go far, go together.”
11. 11
Lessons Learned Learning…
• Importance of governance (but
need to be flexible)
• Different cost models (may be
confusing)
• Demonstrate value (metrics,
feedback)
• Importance of integrated project
management
• Communication (service
changes, maintenance,
procedures, etc.)
• Risks of tool sprawl
12. 12
Next Steps
• Continue to evolve model,
governance, technical framework,
partnerships
• Grow and respond to community
– content editors,
communicators, developers, and
units
• Mobile
• UNC System/Higher Ed
outreach
• Collaboration opportunities
with you?
• How might this model apply
to different service offerings
beyond web and UNC-CH?
** BILLY*** Show of hands…Summarize CMS landscape at that timeDuplication of resources(themes, resources, widgets) Art Department story
** BILLY **March, 2011 – ProposalAgreed on one CMS– Chose WordPress based on success of web.unc.eduDiscussed model – How to meet a very wide range of needs in a scalable model
** Billy **Staff split between both teams (MOUs, technically ITS staff administrative standpoint Supporting each others customers