NORTH CAROLINAOpen Source, OpenPublic, OpenShift

INTRODUCTIONS

Billy HyltonDIGITAL SERVICES DIRECTOR

State of North Carolina

Felicia HaynesACCOUNT DIRECTORPhase2

THE PROBLEM

THE LOOK

THE TECH

None of the above✓

GOAL:

Consistent, Responsive,Usable, and

Easy to Manage

SOLUTION

WHY OPEN SOURCE? WHY DRUPAL? • Freedom

(Not beholden to a vendor)

• Security

• Flexibility and customization

• Collaboration opportunities

• Cost savings

• Huge govmarket share

• Enterprise-ready

• Developer community

• Platform extensibility

• Secure

WHY OPEN SHIFT?• Lack of LAMP stack resources

in State

• Fewer backend/infrastructure staff needed

• Cost savings

• Automated scaling

• Rapid website instance setup

• Application development

WHY OPENPUBLIC?

• Drupal distribution maintained by Phase2

• Used by numerous government organizations

• Provides extensive baseline of functionality

SIMPLE FLEXIBLE

CODE BASES

DATABASES

INTEGRATION OF APPS

SINGLEMULTIPLE

SINGLEMULTIPLE

STARTS HERE

PLATFORM CONFIGURATION COMPONENTS

CUSTOMIZE SELECTION BASED ON BUSINESS NEEDS

Sectioned Site Platform

Platform with Apps

Platform Distribution

Distribution

Allows variety of functionality

Allows variety of content and usersENDS HERE

PLATFORMS SHARE HOSTING, TESTING TOOLS, BUILD TOOLS

PLATFORM FUNCTIONALITY SPECTRUM

SIMPLE FLEXIBLEFeature Divergence

Independence of Site ContentSpeed of Extensbility

Life Cycle Independence

Shared Content Simultaneous DeploymentsConsistency Ease of Maintenance

PROCESS

DESIGN & IA

COLLABORATE

• Working group ofvarious agencies

• Complete review of the various needs and content

• Set a group of common features for common needs

COLLABORATE

COLLABORATE

COLLABORATE

OUTCOMES

DESIGN SAMPLES

FEATURES OF THE PLATFORM

• Blogs, calendars, profiles, search, data tables, documents, LDAP integration, press releases

• Responsive, mobile ready site

• Custom landing pagesto support a modular,flexible design

LESSONS LEARNED

QUESTIONS?

THANK YOU!

Billy Hylton@publicrealm

Felicia Haynes@fhaynes