Your SlideShare is downloading. ×
Practical Guide to Selecting a Web CMS for State and Local Governments
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Practical Guide to Selecting a Web CMS for State and Local Governments


Published on

Acquia webinar from 5/3/2013.

Acquia webinar from 5/3/2013.

Published in: Technology

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Security.
  • Tablets and smartphones are changing the way people consume information and is ready. Whether it’s reading a press release, renewing a license, checking fall foliage conditions, or looking for agency contact information, you can get it done at your desk, on a train, or from the comfort of your own home. You can even sign up to get notified by text message or email from state agencies for the specific topics you care about, such as weather alerts, news, road construction, fishing tips, lottery numbers, and state flag display etiquette.
  • Transcript

    • 1. The Practical Guide to Selectinga New Web CMSFor State and Local Governments
    • 2. PresentersTom Wentworth, CMO at Acquia- 13 Year CMS veteran at vendors Interwoven and Ektron.- @twentworth12 on TwitterNikhil Deshpande- Responsible for the digital presence and strategy for theState of Georgia’s official web portal, User interface designer and a certified usability analystwith more than 10 years of digital media experience- @nikofthehill on Twitter
    • 3. What You’ll Learn in this Webinar• Why Now is the Right Time to Select a New CMS- Mobile, Social, Open• Running a CMS Selection Process- Defining requirements- Selecting vendors- Vendor demonstrations and presentations- Selecting an implementation partner• State of Georgia Case Study
    • 4. 2003-20102010 +First Generation CMS• Brochureware websites• Vendor pioneers Interwoven, Vignette• CMS part of Enterprise ContentManagement SuitesSecond Generation CMS• Dynamic Websites• Marketing-driven• Business results focusedThird Generation CMS• Mobile, Social, Personal, CloudHistory of CMS1994-2003
    • 5. Legacy CMS Challenges• Mobile sites are an afterthought, or impossible• They are expensive to own- High maintenance costs- Difficult to find experienced development resources• Plagued by Usability issues- Products were designed before the advent of modern userinterface best practices- Return of the “Webmaster Bottleneck”• Require multiple point solutions- Social communities
    • 6. • 29% of Black Americans have no Internet access• 51% have no broadband access at home• 32% of Hispanic Americans have no Internet access• 49% have no broadband access at home• 38% of Americans who make less than $30,000/year haveno Internet access• 59% have no broadband access at home• 46% of Americans with a disability have no Internetaccess• 59% have no broadband access at home• 57% of Americans with no high school diploma have noInternet access• 88% have no broadband access at homeSource: Karen McGraneMobile First?
    • 7. Yet 88% of Americans Have a Mobile Phone
    • 8. We Need a Mobile First Approach:Responsive Design
    • 9. One Design. Multiple Layouts.
    • 10. Citizen Engagement. Everywhere.
    • 11. Open Government
    • 12. Open Data, Always Available
    • 13. Running a CMS EvaluationIdentifyRequirements +StakeholdersDefineVendorShortlistRFPVendorEvaluationsSelections+ Contracts* Allocate 3-6 Months for Evaluation
    • 14. Simplified Content Management LifecycleCreate• In-LineEditing• StructuredContentAuthoring• Drag andDrop PageCreationManage• Workflow• Taxonomies• Metadata• PermissionsPublish• ContentReuse• Multi-format• Multi-language• Multi-site
    • 15. Key RequirementsContent Authoring• Inline Editing- Edit content in-place• Structured ContentAuthoring- Forms-based• Drag + Drop PageCreation- Assemble pages withoutdevelopers• Image Management- Resizing, Cropping
    • 16. Key RequirementsWorkflow• Approval Process forPublishing- Draft, In-Review, Published• Version History- Quickly compare versions• Audit Trails- Capture feedback onchanges• Reporting- Bottlenecks
    • 17. Key RequirementsMulti-lingual + Content Re-Use• Separation of Content fromPresentation- Create content once, re-use inmultiple locations- Categorize content usingtaxonomies for automatedplacement• Manage content in multiplelanguages- Manual or automation translationsupport- Define relationship betweenlanguages
    • 18. Key FeaturesSecurity + Permissions• Users- Authorized CMS users• Groups- Collections of users andother groups.• Permissions- Define access levels tofolders and content• Roles- Define access privilegesto users and groups
    • 19. Key FeaturesSocial Communities &Collaboration• Blogs• Networking, Friending, and Following• Ratings + Reviews• Collaboration• ContentModeration
    • 20. There are Lots of Vendors…
    • 21. Defining a Vendor Shortlist• Pick a Development Platform(s)- .NET, Java, PHP• Pick a Deployment Model- Cloud, On-Premise• Select Vendors to Evaluation- Work with Analysts• Forrester, Gartner, Digital Clarity Group, Real Story Group, others- Evaluate Products• Downloads, Trials- Engage Partners
    • 22. Picking a Development PlatformAnd Does it Matter?• .NET Framework- Microsoft-only- Mature development environment• Java- Cross-platform- Popular among larger enterprises and specific verticals likefinancial services• PHP- Cross-platform- Fastest growing CMS development platform
    • 23. PHP Content Management SystemsGrowing Fastest
    • 24. Open Source vs. Proprietary CMSTop Five Myths About Open Source WCM1. Open Source is just for blogs and simple sites2. Open Source isn’t secure3. Open Source won’t scale to handle the world’s largestsites4. Open Source requires tribal knowledge5. Open Source won’t work well with my marketingtools
    • 25. Building a good RFP• Project overview- Provide a detailed written description of the problems you are tryingto solve.• Process- Clearly describe your end-to-end evaluation process w/ timeframes• Requirements- Articulate your requirements. Avoid “Yes/No” questions in favor ofopen ended• Scenarios- Frame your requirements into actual real-world usage scenarios butdon’t prescribe the solution
    • 26. Evaluate ScenariosOkay Example• The Press Release module is one of the most heavily used featuresof our current CMS. Demonstrate how to create and post a pressrelease.Great Example• One of the major weaknesses of the current CMS is not having theability to create a new website. Demonstrate how to create a newwebsite including:• Creating a homepage• Developing templates and style sheets for the underlying pages. Templates will carry the samefooter across all pages of the website.• Creating a subsite with a different homepage but with design elements that tie it to the overallwebsite.• Show how subsites work with a different domain (e.g.,
    • 27. Vendor Presentations… or the Dog & Pony Show• Allocate enough time to cover yourscenarios and requirements- Typically 90-120 minutes• Ask the vendor to bring the rightresources- The Sales Engineer is your friend• Ask the vendor to minimize the“About Us” pitch- Important, but should have already beencovered during initial diligence• Segment the presentation byaudience- Developers/Designers vs. Business Users
    • 28. Evaluate Usability not Curb Appeal
    • 29. Typical License and Deployment Models• Deployment Model- On-Premise: Software is deployed on owned servers.- Cloud: Software is deployed in the cloud.- Hybrid: Authoring servers on-premise, delivery servers inthe cloud• License Types- Perpetual: You buy the software up-front, and pay thevendor a yearly fee for access to upgrades and support.- Subscription: You rent the software, services, and supporttypically on an annual basis.- Open Source: No software license fee. Vendors likeAcquia provide support.
    • 30. Selecting an Implementation Partner• Working with VendorProfessional Services vs. anImplementation Partner• Types of Partners- Global, Regional, etc.• What is their implementationmethodology?• Do they understand your keydrivers?• What is their comfort level withthe technologies?- You’d be surprised…
    • 31. Don’t Forget about Training!• For Developers- Learn the fundamental concepts and techniques for developingCMS applications, including page design, APIs, contentmodels, and more.• For Administrators- Lean server administration concepts and best practices, frominstallation and configuration through ongoinghealth, performance, and availability.• For End Users- Teach users the basics of content management includingauthoring, workflow, and publishing.
    • 32. Case Study
    • 33. WE NEED HELP!• Proprietary CMS• 2 versions• Cost
    • 34. Choosing a New CMS
    • 35. WE <3 DRUPAL• Second largest CMS worldwide• Worldwide community of support anddevelopers• Open source!
    • 36. GOING OPEN SOURCE• Security• Free• Total cost of ownership• Is it ready for “prime time”?
    • 37. Community
    • 38. PLATFORM• Multi-site, multi-database• Single code base• Cloud hosting• Search• Responsive design
    • 39. CONTENT FIRST• Content beyond pages• Design based on data and userexpectations
    • 40. 55 REDESIGNS?• Template based• Styletiles• Demo websites
    • 41. Classic Patriotic Friendly OfficialRedesign