cms assessment committee

158
CMS Assessment Committee Phase I Report Executive Summary Phase One Methodology and Overview The CMS Assessment group membership is comprised of campus IT professionals with significant website administration knowledge; it is chartered by John Krogman. The committee will report both to John Krogman and MTAG. The committee’s primary goal is to first gather information regarding the use of website Content Management Systems (CMS) on campus. If the data indicates an opportunity to better utilize pooled campus funding, the committee is prepared to engage a second phase, which will put forward enterpriselevel tool recommendations. During this first phase, the committee identified internal and peer institution CMS trends, conducted targeted inperson interviews with 12 campus stakeholders, and collected campuswide data (from over 650 individuals) over a two week period through a survey geared toward current and future CMS usage. The data collected indicates the timing is right to explore options for a new, centrally supported, enterprise caliber CMS. Choosing a new CMS tool will afford campus an opportunity to use existing funding levels to maintain and support a significantly larger percentage of CMS based websites, in addition to the potential real money and opportunity for cost savings that could be realized by units through voluntary aggregation and shared services. In addition, aggregation of websites using a widespread CMS tool would potentially lower the overall risk platform for campus while freeing up security team cycles. User feedback indicates a strong desire for a centralized library of resources, themes, and plugins, however existing distributed campus users would likely be slow to migrate to a centralized CMS. Better CMS alignment on campus would allow centralized development of a library of resources, themes and plugins and a pathway to more centralizing. Our current campus CMS tool, OpenText (formerly RedDot) was chosen during an RFP process in 20072008. It is comparatively expensive to maintain the license ($79k) and infrastructure ($86k), which are covered through campus assessment. Even though web development and technical support services are available at no cost to end users, to date OpenText has been adopted by approximately 10% of campus web sites. According to data collected in the survey, current users of OpenText that are planning a website migration are overwhelmingly looking at other tools, despite their strong satisfaction with the support provided by the WiscWeb CMS team.

Upload: vuongtu

Post on 14-Feb-2017

229 views

Category:

Documents


3 download

TRANSCRIPT

  • CMSAssessmentCommitteePhaseIReport

    ExecutiveSummary

    PhaseOneMethodologyandOverviewTheCMSAssessmentgroupmembershipiscomprisedofcampusITprofessionalswithsignificantwebsiteadministrationknowledgeitischarteredbyJohnKrogman.ThecommitteewillreportbothtoJohnKrogmanandMTAG.ThecommitteesprimarygoalistofirstgatherinformationregardingtheuseofwebsiteContentManagementSystems(CMS)oncampus.Ifthedataindicatesanopportunitytobetterutilizepooledcampusfunding,thecommitteeispreparedtoengageasecondphase,whichwillputforwardenterpriseleveltoolrecommendations.Duringthisfirstphase,thecommitteeidentifiedinternalandpeerinstitutionCMStrends,conductedtargetedinpersoninterviewswith12campusstakeholders,andcollectedcampuswidedata(fromover650individuals)overatwoweekperiodthroughasurveygearedtowardcurrentandfutureCMSusage.Thedatacollectedindicatesthetimingisrighttoexploreoptionsforanew,centrallysupported,enterprisecaliberCMS.ChoosinganewCMStoolwillaffordcampusanopportunitytouseexistingfundinglevelstomaintainandsupportasignificantlylargerpercentageofCMSbasedwebsites,inadditiontothepotentialrealmoneyandopportunityforcostsavingsthatcouldberealizedbyunitsthroughvoluntaryaggregationandsharedservices.Inaddition,aggregationofwebsitesusingawidespreadCMStoolwouldpotentiallylowertheoverallriskplatformforcampuswhilefreeingupsecurityteamcycles.Userfeedbackindicatesastrongdesireforacentralizedlibraryofresources,themes,andplugins,howeverexistingdistributedcampususerswouldlikelybeslowtomigratetoacentralizedCMS.BetterCMSalignmentoncampuswouldallowcentralizeddevelopmentofalibraryofresources,themesandpluginsandapathwaytomorecentralizing.OurcurrentcampusCMStool,OpenText(formerlyRedDot)waschosenduringanRFPprocessin20072008.Itiscomparativelyexpensivetomaintainthelicense($79k)andinfrastructure($86k),whicharecoveredthroughcampusassessment.Eventhoughwebdevelopmentandtechnicalsupportservicesareavailableatnocosttoendusers,todateOpenTexthasbeenadoptedbyapproximately10%ofcampuswebsites.Accordingtodatacollectedinthesurvey,currentusersofOpenTextthatareplanningawebsitemigrationareoverwhelminglylookingatothertools,despitetheirstrongsatisfactionwiththesupportprovidedbytheWiscWebCMSteam.

  • NarrativeSummary

    IntroductionInrecentyears,theuseofwebsiteshasexplodedontheUniversityofWisconsinMadisoncampus.Atpresent,thereareatleast1900separateUWrelatedwebsites.Theyareusedbygroupslargeandsmall,forpurposesaswiderangingassharingresearchdata,tobroadcastingphotosofplants,tosellingartwork,tocollaboratingbetweenteamsscatteredacrosscontinents.Toaddresstheirneeds,manyunitshaveutilizedtheirowninternalstaffingandinfrastructuretodevelopandhosttheirwebsites.Additionally,somegroupswithintheUWcommunitycontractedwiththirdpartywebsitevendorstodevelopcustomwebsites,thenhiredtheirownITsupportstaff.Oftentimes,websitesareputupbyagraduatestudentandthenorphanedwhenthatpersonexitstheprogram.CampusgroupshavelookedtoDoITforguidanceandsupport.Forthesakeofefficiency,branding,andofferingguidanceforthosewhoneedit,theUWneedstomapoutastrategytoaddressthiscritical,andradicallyshiftinglandscape.DoITisveryinvestedinworkingwithcampustoworkonafuturestrategyforCMS.InAugustof2015,JohnKrogman,DoITCOO,constitutedacommitteetoconductacampuswideevaluationofthiseverevolvingwebsiteenvironmentoncampus.Thiscommittee,calledtheUWCMSAssessmentCommittee,ischairedbydistributedITandcomprisedoftwelveindividualswhorepresentabroadcrosssectionofdepartments,schools,andexperiences.Thisreportpresentsthecollectivefindingsofthatcommittee.TheCMSAssessmentCommitteeneededtogatherinformationfromnumeroussources.SubcommitteeswereformedtoconductfacetofaceinterviewsofUWMadisonstaff,tocontactpeerinstitutions,tocollectusageonourowncampuswebsitecommunity,toanalyzethedatathatwasreturnedthroughoursurvey,andtocraftthevariouscomponentsofthisreport.Throughcommitteemeetingtime,andgoogledocumentcomments,mainthemeswerepulledfromthesubgroupsreports(seeAppendixI),andturnedintothisreport.

    GatheringInformationTobetterunderstandtheCMSlandscapeoncampus,thecommitteeconductedtwelvefacetofaceinterviewswithUWgroupswhohadrecentlybuilt,orrebuilt,theirwebsites,orwereotherwiseinvolvedintheUWwebsitesituation.(SeeAppendixI,1on1Themes)Duringtheseinterviews,weaskedaboutthedecisionsthatweremade,theprioritiesthatwerepursued,andultimately,whatguidedthegrouptomakethedecisionstheymade.

    CMSAssessmentCommitteeFinalReport Page2of10

  • Somerecurringthemesencounteredduringtheseinterviewsinclude: Thereisinterestincentralizedsupportforvariouswebneedsoncampus. Thereisalsoastrongdesireforvariousdegreesofautonomy. Campuswebsiteownersarelargelyexpectingtoprovideandedittheirownwebsite

    content. Astrongdesireforeasytoaccessbranding,pictures,UWdatafeeds,andplugin

    support. Acrosscampus,thereisbroadsupportfor(anduseof)multiplewebsiteplatforms.The

    threemostcommontoolsareWiscWebCMS,Drupal,andWordPress. TheWiscWebCMS,OpenText,hasamixedreceptiononcampus. TheserviceandsupportteamforWiscWebCMShasaverystrongreputationon

    campus. Manygroupsoncampusarewillingtospendasignificantamountofmoneyforcustom

    developmentandhostingoftheirwebsites,whileothergroupsneedafreeservice. Oneofthemainthemeswaseaseofuseforcontenteditors,whichfrequentlywasakey

    factorinthenextCMSselection. Adesireforoptionalworkflowcontrol. Significantfrustrationwhenasitewasdependentondevelopersupportwhenthearea

    haddeveloperturnover. Instantaneouspublishingwhenthepublishbuttonispressed.

    AQualtricssurveywasconductedtodeterminewhattoolspeopleareusing,andwhythosetoolsarebeingchosen.Thesurveyutilizedsmartlogictokeepthequestionsrelevantbasedonpreviousresponses.Iftheyhadrecentlymigrated,weaskedthemabouttheiroldsiteandreasonsformoving.Weaskedabouttheircurrentsite.Andiftheyplannedtomigratewithinthenexttwoyears,weaskedthemaboutwhattheyweremigratingto.Wehadover650responses,thevastmajoritywerefromDrupal,WordPress,andWiscwebusers.InadditiontoemailstoTechPartnerPrimesandMTAG,wealsosentthesurveytotheDrupal,WordPress,andWiscwebusergroups.DoIThostingsentthequestionnairetoalltheircustomers,andDoITsPTEsentthesurveytotheattendeesofCMSrelatedtraining.Acouplestandouts

    WordPressisgrowingover50%ofthemigrationsinthenexttwoyears. Functionalitywasthetopprioritywhenchoosingnewwebsites.

    Anumberofsimilaruniversitieswerecontactedandaskedsimplifiedquestions,usuallywithaphonefollowuptoseewhattheyweredoingforenterprisesolutions.

    CMSAssessmentCommitteeFinalReport Page3of10

  • CurrentUWMadisonOfferingUWMadisonoffersoneenterpriselevelwebpublishingtool:OpenText.ItissupportedcentrallybyDoITsWiscWebCMSEnterpriseService,isfundedthroughacampusassessment,andisavailableatnoadditionalcosttothosewhouseit.OpenTexthasasmallbutloyalfollowingofuserswhoareverypleasedwiththetool.AlmostallwhorespondedwerepleasedwiththesupportprovidedbytheWiscWebCMSteam.However,manygroupsoncampushavedecidedtonotuseOpenText,becausetheydeterminedthatthetooldidnotmeettheirgroupsneedshowever,giventheabsenceofcentralsupportforothertools,thesegroupswerelefttofindandfundsupportontheirown.OpenTextisastaticwebsitegeneratorthatpushescontenttowebservers.ThisisaverydifferentmodelthanthecurrentcropofCMSwheretheabilitytoeditisembeddedwiththehosting.ModernCMSmakemuchbetteruseofsharedresources,requiringfewerstaffandvastlycheaperhostingcostspersite.Inparticular,DrupalandWordPresshavebecomecommonplaceinbothcorporateandhighereducationcreatingarobustusercommunitywithinnumerableenhancement(plugin)options.UWMilwaukeeperformedanexhaustiveinvestigationintodifferentCMSoptions,lookingatusabilityandlongtermcostbeforerecentlysettlingonWordPress.OtherlargecampusesmadethemovetoDrupalaftersimilarstudies.UWMadisoncampususersarealsomakingthemove.Over50%ofplannednewsiteswilluseWordPress.

    CurrentStateIssuesWealsosawasmallbutsignificantnumberofsitesthatareworkingwithoutsidevendorsfordesign.Thereislimiteddesignsupportoncampus.Whilethisisntnecessaryanissue,sincethereareanumberofcommercialdesigncompaniesabletostepin,itisconcerningthatthedesignerstendtoproposenewCMSoptionswhichfurtherdiversifythecampusinstalledCMSbase.WedidhearthatdesignfirmsdesignedforWordPressorDrupalbutnotOpenText.Theresultleavessomecampusunitsonaplatformforwhichtheyhavenosupport.Wealsoinvestigatedseveralsharedhostingoptionsoncampus.WefoundthatmultihostedWordPressandDrupalwereafractionofOpenTexthostingcostsandfrequentlyhadfewerstaffsupportingthemwithasimilarportfolioofservicetoWiscWebCMS.Wealsoinvestigatedafewcloudvendors,andfoundpotential,thoughitwasoftenhardtoeasilygaugefinalcosts.Forinstance,theytypicallychargeforwebcertificates,butthosecanbeobtainedatnocostoncampusduetoasubsidyfromtheOfficeofCybersecurity.Ourreadingofthedatashowsthesetwoareas,campusmultihostsitesandcloudsolutions,shouldbecoveredinadetailinaPhaseIIreporttovalidatetheyscaletoenterpriselevelsandwithadequatetechnicaldetailtoabletobeevaluatedforcampususe.

    CMSAssessmentCommitteeFinalReport Page4of10

  • OneoftheareasthatneedstobeexploredisawaytobetterleverageworkdonebyWiscWebCMSforusebymoreofcampus.Anumberofgroupsnotedtheyareunlikelytomovetoacampussolutionbutwouldbeveryinterestedinalibraryofresourcesthattheycanconsume.

    OtherUniversitiesandCorporateWefoundthatuniversitiesweremovingtoDrupalandWordPress.FromGartnerreports,thesearebothstrongcontenders,eachwiththeabilitytohandlemostwebsiteneedswithenergeticdevelopercommunities.GartnernotedthatsupportingbothplatformswouldensurethatallwebprojectscouldfindanappropriateCMStoolfortheirneeds.WealsolookedatreportsonadoptionratesandfoundthatbothDrupalandWordPresshadalargeuserbaseandmarketshare,whileOpenTexthasdwindled.(SeeAppendix4.)UWMilwaukeeinparticularwasveryinteresting.TheyrecentlypickedWordPressastheirenterprisesolutionandaremigratingtoit.TheyinvestedsignificantresourcesinresearchingthebestoptionforCMS,includingusertestingandanalyzinglongtermmaintenancecosts.WordPresswasfoundtobetheeasiestandmostefficientcontenteditor,savingstafftimewheneditingpages.Itwasalsothebestvaluewhenlongtermmaintenancecostswerefactoredin.Itwasassessedrobustenoughtohandlethevastmajorityoftheirneeds.TherewereanumberofotherlargeschoolsthatadoptedDrupal.

    WiscWebCMSFY16Budget DoITLabor 535,000Training 40,000 DoITHosting 76,420

    Servers,Database,Network,Storage,Backup

    Licensing 84,394OpenText 79,000 Depreciation 10,000 Misc 3,150

    Roomrental,advertising,fontservices,etc

    Total 708,964

    CMSAssessmentCommitteeFinalReport Page5of10

  • StatisticsandSurveyAnalysis

    Q:WhatCMSsystemsarerespondentsusingnowtomanagetheirwebsitesandhowmanywebsitesaretheymanagingoneachCMS(question16)?

    CMS Response %Resonse Websites %ofTotal

    WiscWebCMS 145 33% 175 9%

    WordPress 201 45% 658 34%

    Drupal 80 18% 260 14%

    HTML/CSS 144 33% 338 18%

    SharePoint 15 3% 17 1%

    GoogleSites 37 8% 78 4%

    Other1 72 16% 277 14%

    Other2 11 2% 118 6%

    Numbersinthischartreflectonlyuserswhorespondedtothesurvey.ActualnumbersforallCMSsarebelievedtobehigher.

    Q:Whydidyourgroupmigratefromthepriorplatform(s)?(Selectallthatapply.)

    Reason Responses %ofTotal

    dissatisfiedwiththefunctionality(e.g.theabilitytocreatenewpages,editexistingpages,makeminorchangestoappearanceandlayout)

    78 54%

    dissatisfiedwiththetechnicalsupport(e.g.theabilitytodevelopnewfeatures,expandthewebsitesusefulness)

    54 38%

    dissatisfiedwithmaintenance(e.g.maintainingversions,installingpatches,managingbackups,security,etc.)

    55 38%

    dissatisfiedwiththecost 8 6%

    Idontknow 34 24%

    CMSAssessmentCommitteeFinalReport Page6of10

  • Q:Whatwillbeyourprioritieswhenselectionthenextplatform?(Selectallthatapply.)

    Reason Responses %ofTotal

    functionality(e.g.theabilitytocreatenewpages,editexistingpages,makeminorchangestoappearanceandlayout)

    131 89%

    technicalsupport(e.g.theabilitytodevelopnewfeatures,expandthewebsitesusefulness)

    92 62%

    maintenance(e.g.maintainingversions,installingpatches,managingbackups,security,etc.)

    102 69%

    thecost 8 5%

    Idontknow 12 8%

    Q:Whereapplicable,indicateyourgroupssatisfactionwiththetechnicalsupportavailablewiththefollowingwebcontentmanagementplatformsortools.(Note:Responsesrangedfrom1ptto4pts.AlowerAverageValuerepresentsabetter,morepositiveresponse.)

    Reason AverageValue

    WiscWebCMS 2.45

    WordPress 2.62

    Drupal 2.77

    HTML/CSS(e.g.DreamWeaver) 2.68

    SharePoint 3.14

    GoogleSites 2.85

    Other 2.90

    CMSAssessmentCommitteeFinalReport Page7of10

  • PeoplewhohaveWiscWebCMSsites,andareplanningonmigratinginthenexttwoyears.

    PeoplewhohaveWordPresssites,andareplanningonmigratinginthenexttwoyears.

    PeoplewhohaveDrupalsites,andareplanningonmigratinginthenexttwoyears.

    CMSAssessmentCommitteeFinalReport Page8of10

  • WiscWebCMSsatisfactionresultsforpeoplewithWiscWebCMSsites.

    WordPresssatisfactionresultsforpeoplewithWordPresssites.

    DrupalsatisfactionresultsforpeoplewithDrupalsites.

    CMSAssessmentCommitteeFinalReport Page9of10

  • CommitteeListEricGiefer,Chair,LawSchoolRyanEngel,LearningSupportServices(LSS)LibbyPeterek,UniversityMarketingJasonPursian,CALSGriffithRandall,L&SStudentAcademicAffairsGretaSeckman,DivisionofContinuingStudiesAlanSilver,ChemistryDanSimanek,VCRGEJoeTarter,DoITJamesVogel,OfficeoftheRegistrarNickWeaver,UniversityMarketingCliffCunningham,PM,DoIT

    CMSAssessmentCommitteeFinalReport Page10of10

  • Printed11/17/2015

    CMS Assessment Committee Phase I Report Appendix 1 CMS Assessment Committee Findings and Assessment

  • Themesfrom1on1InterviewsIndividualsInterviewedOneonOneMeloneyLinder,SchoolofBusinessBrendaSpychalla,SchoolofEducationAaronStern,OHRAmyToburen,DeanofStudentsOfficeBrianRust,DoITCommunicationsMikePitterle,SchoolofPharmacySteveBarnet,IceCubeAlissaEwer&KathiMatthewsRisley,GraduateSchoolDavidLuke,UWLibrariesBethTobakos,PoliticalScienceDepartmentKellyOLoughlin&AllysonCasey,UWUnionCathyRiley,WiscWebCMS

    ExistingService

    WiscWebCMS,currentlyusingOpenTextasthewebcontentmanagementplatform,hostsapproximately200sitesontheUWMadisoncampus.Theserviceprovidesbothstandardandresponsivetemplates.Customsitedevelopmentisalsoavailable.PublishingisdoneviaSFTPtoaremotesite.Extensivedocumentationisavailable,asistraining.Grouptrainingisofferedseveraltimesamonth,while1on1trainingcanbemadeavailable.WiscWebCMSprovidesaccesstofrontendwebdevelopers,alongwithactivemaintenanceandsecurity.Itwasnotedthatthereareasignificantnumberofpeopleoncampuswhodonthavefundingforawebsite(s)and/ordonthaveaccesstowebdevelopers.Thiscommunity,inparticular,isakeydriverbehindtheexistingservices.

    Themes:UsageTrends

    AnumberoflargecampusentitieshaverecentlychosentomigrateawayfromWiscWebCMSorneveradoptedtheplatform.Themostcommontargetplatform(s)forcampusentitiesnotusingWiscWebCMSareclearlytheopensource,PHPbasedwebCMSplatforms,WordPressandDrupalspecificallythoughotherswerenoted.EducationandSchoolofBusinessbothmakeuseofthirdpartycommercialtools,thoughitseemsEducationhasmixedusewithWordpressandmaybeshiftinginthatdirection.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 1 of 23

  • Themes:ReasonsgivenfornotselectingWiscWebCMS

    SeveralreasonswerestatedfornotmakinguseoformovingawayfromtheWiscWebCMSservice.Statedreasonsincluded:

    Userexperienceforeditorsispoor,laborious Notflexibleenoughfordevelopers Slowandcumbersometouse,sometimesrequiringrepeattrainingnotintuitive Tooldoesnotprotecttheendeditorsfromcodeenough Windowsonlyforadministering(nolongertrue) WiscWebCMStimetablesfordeliverycouldbelong

    Themes:Keyfeaturesneededinatool

    AnumberofneedswereidentifiedwhenseekingawebCMStool.Someoftheidentifiedneedsincluded:

    Quickuseoftemplatesandlayouts(brandedlook&exactpagelayout) Quickandeasyediting Imagesliders Formsandworkflows Opensourceplatformandplugins Crosspromotionofevent Responsive/Mobileready Supportfordistributededitors Enforcementofboundariesandcontrolsacrossdistributededitors/contributors. Someinteractivitywithdata Abilitytopullindatafrom3rdpartysites

    Themes:Desireditemsinacentralservice

    Anumberofitemswereidentifiedasdesirableinacentralservice.Theseitemsincluded: Availabledevelopmentandsupportwithoptiontooptoutwhenlocalstaffareavailable Accesstotraining Appropriatesecurityandlongtermmaintenance Abilitytomakechangesquickly Acentralrepositoryofthemesandplugins Abilitytohavepluginswrittenandinstalled Toolstomanageandmovedatabetweentestandproduction

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 2 of 23

  • Delegatedaccesscontrol VerytightshibbolethintegrationandaccessforthoseoutsidetheUW NotconstrainedbyUWlookandfeel Searchengineoptimization(SEO) Addressaccessibility(ADA)issuesandconcerns

    Themes:OtherInsights

    Anumberofcampusentitiesareoutsourcingdesignanddevelopmenttoconsultants,sometimesforsixfigurecontracts

    UseoftheDoITWebHostingserviceappearstobeverycommon Somedonotwanttodevelopormaintainthemselves,soongoingsupporthasbeena

    questionforthosecurrentlyusingWordPressorDrupal SomecustompluginworkhasbeenprovidedfromDoITDesktopSupportandAcademic

    Technology Forthosebuildingtheirownsites,somementionofstaffturnoverorlimitedaccessto

    developmenttime

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 3 of 23

  • OtherSchools&Industry

    Questionsasked:

    1. Do you use a CMS for your homepage?

    2. Are there other CMSes you support?

    3. How long have you used said CMS?

    4. Who made this decision?

    5. Are you happy with it?

    NotreDame

    1. Do you use a CMS for your homepage? We do not use a CMS for www.nd.edu. It's pretty much a simple PHP class and

    we update the pages directly on a staging server.

    2. Are there other CMSes you support? Our primary CMS on campus is an in-house built Rails app called Conductor

    (http://conductor.nd.edu/) which manages approx 480 websites. We also have a Wordpress Multisite install that runs our blogs.nd.edu network. The Engineering department uses Plone, but my team is not involved in that product.

    3. How long have you used said CMS? We have used Conductor since 2007.

    4. Who made this decision? Our web team decided to build a CMS because the solution at the time

    (Contribute and Dreamweaver) were underwhelming, and none of the other open-source CMS's at the time were very interesting.

    5. Are you happy with it? We are very happy with Conductor. We have been able to craft it over the

    years to fit our needs very well.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 4 of 23

    http://www.nd.edu/http://www.nd.edu/http://conductor.nd.edu/http://blogs.nd.edu/http://blogs.nd.edu/

  • UTAustin

    1. Do you use a CMS for your homepage? Yes Drupal 7

    2. Are there other CMSes you support? Yes, Wordpress only.

    3. How long have you used said CMS? Weve been on Drupal for 8 years.

    4. Who made this decision? Combination of the central IT web team and University Communications.

    5. Are you happy with it? Absolutely! The only downside is that it has become difficult to find, hire, and

    retain good employees because the demand for Drupal developers is so high in Austin.

    UniversityofMichigan

    1. Do you use a CMS for your homepage? No, customized platform for umich.edu gateway utilizes a robust php/MySQL

    framework

    2. Are there other CMSes you support? Yes, Wordpress for two primary reasons Ease of use for content stewards Ease of use in keeping secure

    3. How long have you used said CMS? Several years

    4. Who made this decision? UMich Creative team

    5. Are you happy with it? Yes, very.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 5 of 23

  • UniversityofIllinois

    1. Do you use a CMS for your homepage? No - Dreamweaver and static files

    2. Are there other CMSes you support? There is no centralized solution. Several instances of Wordpress and Drupal on

    campus. Even within each school or college, different CMSes are used.

    3. How long have you used said CMS? N/A

    4. Who made this decision? Each unit makes their own decision based on experience and expertise.

    5. Are you happy with it? The web services team has created several applications within what they call

    the Tool box They include, but are not limited to: calendars, blogs (home built), directory, maps, email, shortened URLs, and Form and survey builder. All of these applications can be pulled into any of the various web solutions used around campus. The web services team is happy with their solution but cannot speak for the rest of campus.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 6 of 23

  • UniversityofWisconsinMilwaukee*

    1. Do you use a CMS for your homepage? Yes, UWM uses CommonSpot by PaperThin for the UWM Home Page and some

    top level (university-wide) web page content on www4.uwm.edu. CommonSpot used to host most of the school/college and administrative unit content as well. We are transitioning to WordPress (multisite) with a UWM-branded theme and curated catalog of plugins residing on web host that simply has the uwm.edu domain (no www4). Most schools/colleges have moved to WordPress (e.g. http://uwm.edu/business/) and we are actively working on moving the remaining campus units to WordPress, as well as the UWM Home Page and top level page content that remains on CommonSpot. WordPress infrastructure is hosted at AWS. University Relations & Communications supports the WordPress software for campus.

    2. Are there other CMSes you support? CommonSpot and WordPress for organizational unit-level outward-facing web

    content. CommonSpot is still supported but is colloquially considered a legacy service. We have not yet started a formal retirement project. We are in the process of rolling out another WordPress-based web publishing service for faculty and staff professional pages (e.g. people.uwm.edu/rothfels). The provider is CampusPress. UWM is also in the process of rolling out Office 365 Sites (SharePoint). I believe SharePoint will be primarily targeted at internal audiences, but I mentioned it because it does have CMS capabilities.

    3. How long have you used said CMS? CommonSpot since late 2007. WordPress since March 2014.

    4. Who made this decision? In both instances, a campus working group conducted research, gathered

    feedback, produced requirements, vetted candidates, consternated slightly, and issued a recommendation. Both working groups were sponsored by UWM's Web Steering Committee.

    5. Are you happy with it? WordPress was selected in May 2013 as an alternative to CommonSpot, based

    on a campus working group recommendation. The campus working group was formed in June 2012 to assess CommonSpot service/functionality gaps that had become apparent as the CMS landscape evolved in the time since we first selected CommonSpot. WordPress has been well-received on campus, is efficient to work with, and has proven to be approachable by a wide audience of content authors/owners. We have experienced a quite significant reduction

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 7 of 23

    http://uwm.edu/business/http://uwm.edu/business/

  • in development and support hours with WordPress, as well as a significant decrease in time required for web-related project completion with WordPress.

    * On the phone, Mark walked me through their process. It was very helpful. They did a lot of things right like measuring time and cost for ongoing support of a new system and a high level usability test of the most common tasks in Drupal, Wordpress, and their current system. From those tests, it was revealed that Wordpress was 6x more efficient than any of the other CMSes in completing basic tasks (i.e. fixing a typo, adding a pdf, inserting a photo with caption, inserting a photo gallery, etc.) Hes sending some of their documentation over in the morning. (11/5/15)

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 8 of 23

  • Managed/EnterpriseWebHosting

    UWMadisonhasawellestablishedhistoryofbuildingandmaintainingtheinfrastructurenecessarytosupportitsteachingandresearchmissions,includinghostingsolutionsforwebsitesandwebapplications.However,giventheproliferationandwidespreadadoptionofcloudservicesinmanyareasoftheITlandscape,itwouldberemissofthiscommitteenottoincludeacomparisonofsomecloudservices/serviceprovidersinitsreport.GiventhescopeoftheuniversitysonlinepresenceandthemanyhundredsofwebsitesassociatedwiththeUW,thiscomparisonfocusesonahandfulofenterpriselevelproviderscompetinginthecloudbased,hostedwebcontentmanagementspace.Vendorsinthisspaceuseavarietyofmechanismsfordeterminingpricing,makingastraightcomparisonoftheincludedvendorsdifficult.Onewaytoelicitamoredirectcomparisonwouldbetoprovideeachvendorwithasamplehostingscenariobasedononeormoreknownhostingenvironmentscurrentlyinproductionattheuniversityandthatincludesamatrixofhigh,medium,andlowvisibilitywebsites,monthlyvisitortraffic,theaveragediskpersite,natureofthecodebase(singleormultisite),etc.,alongwithlesscommonlyusedrequirementslikeSolrsearchoracachingsystem.WerecommendincludingsuchanexerciseinPhaseIIofthiscommitteesproject.Thevendorsincludedinthisreportwerechoseninpartbecausetheyhaverelativelyequivalent,comparablefeaturesets,includingawrapperofservicearoundthecontentmanagementsystemseachvendorprovideshostingforthesevendorsalsoprovidespecializedtoolstomakeadministeringthosesystemseasier.AmorecomprehensivecomparisoncouldincludevendorslikeAmazonWebServicesorRackspacebutwithacknowledgementthatitwouldbeuniversitystaffprovidingthewrapperofsupportandmaintenanceofanyspecializedadministrationtoolsandnotthehostprovider.

    BlackmeshBlackmeshisafullymanagedwebhostingproviderfoundedin2003.Blackmeshfocusesonprovidinghighlyflexible,customizedhostingsolutionsbasedoncustomerneedsitalsoprovidesfullservicesupportforWordPressandDrupalbasedwebsites.

    FeaturesandServiceConfiguration: Hosting/infrastructure:Drupal,OpenText,Wordpress,oranyotherserviceortool Service/support:Willinstall,configure,andsupporteverythingfrominfrastructureupto

    code Compliance/Security:FedRAMP,FISMA,HIPPA,PCI Serverstability/uptime:99.999%stabilitywrittenintoSLAcontract Additionalservices:ApacheSolravailabilityandsupport,SAMLintegration Developmentenvironment:flexible/customizablepercustomerneeds

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 9 of 23

  • Infrastructurebuiltusingdedicatedresourcesnotasharedhostingenvironment Datacenterinformation:USbasedlocatedVirginiaandNevada Brag:claimstocostapproximately30%lowerthancompetitorsbutwithhigherlevelsof

    service

    Pricingbasedon:1. NumberofCPUs2. Amountofram3. Sizeofdisk/storagespaceused4. Complexityofsystem5. Traffic

    Customersinclude:JohnsHopkinsUniversity,DepartmentofEnergy

    PantheonPantheonprovidesascalablewebsitemanagementplatformforWordPressandDrupalwithintegrateddeveloper,workflow,andautomationtools.PantheonofferstiersofservicerangingfrompersonalwebsitesuptoPantheonEnterpriseandPantheonforEdu.

    FeaturesandServiceConfiguration: Hosting/infrastructure:WordPressandDrupalhosting Service/support:Elitetierincludesunlimitedtickets2hourresponseSLAguaranteed,

    phonesupport,and24x7oncallsupport Compliance/Security:RecommendsagainsthostingFERPAdataonPantheon

    infrastructure Serverstability/uptime:99.9%(Elitetiercustomersonly) Additionalservices:ApacheSolrv3.6deliveredasaservice,VarnishandRedis

    (caching),DenialofServiceProtection,NetworkIntrusionProtection Developmentenvironment:

    Developerdashboardwithoneclicksiteprovisioning oneclickcoreupdatestoapplyWordPressandDrupalsecuritypatches separateDev,Test,andLiveenvironments

    Pantheondoesnotsupporttraditionalmultisiteinstallationsinstead,theyprovidecustomupstreams/distributionsthatallowindividual/departmentwebsiteownerstolaunchsiteswithcentrallyadministeredbrandingandtemplates(Enterpriselevelonly)

    Rolebasedpermissionstocontrolsite/team/department/individualowneraccesswithinanorganization

    Datacenterinformation:USbaseddatacentersprimaryhostinglocatedatRackspaceinChicago

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 10 of 23

  • Brag:PantheonistheworldsfastesthostingforDrupalandWordPress.MultipleindependentbenchmarkshavecomparedPantheonwithotherproviders,andweconsistentlycomeoutontop.

    Pricing(PantheonEnterprise):PantheonpricingisorganizedaroundtheirPersonal,Pro,andBusinessplanlevels.PantheonEnterpriseincludesa$10,000annualselfservicecreditthatisusedtomanagemultipleselfserviceplans(Personal,Pro,Business).Ownersofindividualsitesthenselecttheappropriateplanbasedonasitespageview,storage,RAM/memory,etc.,needssiteownerscanswitchbetweenplansbasedonevolvingsiteneeds.PantheonforEduincludesfreehostingfordevelopmentsiteschargesbeginonlyafterasiteislaunched.Pricingfortheselfserviceplansisasfollows:

    Personal:$25/monthwithupto10,000monthlypageviewsand5GBstorage Professional:$100/monthwithupto100,000monthlypageviewsand20GBstorage Business:$400/monthwithupto500,000monthlypageviewsand30GBstorage

    Customersinclude:ArizonaStateUniversity,Columbia,MIT,Princeton,UCBerkeley,UniversityofMinnesota

    Acquia/WPEngineAcquiaisalargescaleDrupalonlycloudplatformprovider,thoughfortheUniversityofTexasatAustin,AcquiapartneredwithWPEngine,itselfaWordPressonlyhostingservice,toprovideacomprehensiveenterprisehostingsolution.

    AcquiaFeaturesandServiceConfiguration: Hosting/infrastructure:Drupalhosting Service/support:24x7supportforcriticalissueswithnon24x7supportforotherissues

    (AcquiaCloudEnterprisetier) Compliance/Security:HIPPA,FISMA,PCI Serverstability/uptime:99.95%SLA Additionalservices:VarnishandMemcache(caching)ApacheSolrsearchMollom

    (spamblocker)AcquiaContentHub(acloudbased,centralizedcontentsyndicationtoolthattiesintomanypopularcontentmanagementsystems)

    Developmentenvironment: development,staging,andproductionenvironments easydeploymentofcode,files,anddatabasesbetweenenvironments Drupalcoreandmodulesecuritypatching automatedtestsmonitorandflagissuesascontentismigratedbetween

    environments GITandSVNsupport

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 11 of 23

  • Drushintegration EnterprisecontractsusuallyacombinationofSiteFactory(6080%ofsites)andAcquia

    Cloud(2040%).SiteFactoryisrelativelylockeddownwithlittlecontrolofunderlyinginfrastructureAcquiaCloudprovidesmoreaccesstotheunderlyingplatform.

    Datacenterinformation:USbaseddatacentersinOregonandVirginia

    WPEngineFeaturesandServiceConfiguration: Hosting/infrastructure:WordPresshosting Service/support:24/7technicalsupportfromUSbasedWordPressexperts Compliance:PCI Additionalservices:Evercache(caching),builtinenterpriseCDN Developmentenvironment:

    stagingareawithoneclickpushtolive gitpushintegration

    AutoapplicationofminorpatchesWPEnginetestsmajorpatchesbeforerecommendingcustomerupgrades

    RealtimesecuritythreatdetectionmonitorsagainstDDOSandbruteforceattacks,intrusiondetection,Javascript/SQLinjection,XMLRPCattacks,andothervectors

    Automaticbackupanddisasterrecovery Datacenterinformation:USbaseddatacenterslocatedintheMidwest Brag:Ifyougethacked,wellfixitforfree.

    Pricingbasedon:ThecomplexityofajointpricingcontractwithAcquiaandWPEngineisbeyondtheabilityofthisreporttoestimate.AcquiahasaflexiblepricingsolutionthatincorporatesfactorsincludingamountofCPU/RAM,sitestorage,numberofPHPprocesses,numberofcodebases,andsupportneeds.WPEnginesbasicpricingisorganizedaroundasystemofhostingplansbasedoncodebases,pagevisits,anddatastorage.WPEnginealsohasaPremiumandEnterpriseplans.

    Customersinclude:UCLA,Harvard,UTAustin

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 12 of 23

  • CampusSummaries

    WiscWebCMS #Sites:around200 #staff:6.5FTE,representingthefollowingrolls:ProjectManager,Application

    Administrator,SupportConsultant,ApplicationDevelopers,DatabaseAdministrator,EndUserandAdministratorTrainers,SystemAdministrator,LDAPAdministrator

    #infrastructurecost(licenses&hardware):$165,420 Service(noninfrastructure)cost:$543,544 Costtouser:$0(ifdifferentlevels,explain) Servicenarrative(acoupleparagraphs,notlongerthanapage)shouldinclude

    support(whodoespatches),security,descriptionofservice(i.e.,design,dev,training,etc),whotheserviceissuitablefor.

    WiscWebCMSInfo: PushtypeCMSfromOpenText,previouslyRedDOT.

    WiscWebCMSServiceNarrative: ProvidesCMShostingforanyUWMadisondept/school/college. http://info.wiscwebcms.wisc.edu/ SupportprovidedbyDoITHelpDeskandtheDoItWiscWebCMSteam.

    NumerouswellwrittenKBarticlescoveredmostenduserandadministrativetopics.

    Usersareadded/removedtoprojectbyWiscWebCMSteam. Teamisveryresponsiveandcustomerfocused. Monthlybrownbagswithenduserstobothsharenewfeaturesandgatheruser

    input. TrainingprovidedbyDoITtraining.Regularuserclasses(3hours),nocostto

    userAdmintraining,2hours,freespecializedtrainingonrequest. WebsitecanbehostedbyDoITCMSteam,orbyDoITWebHosting,oronown

    server CMSserversupportedbyDoITWiscWebCMSteam Providesolderstandardandnewresponsivetemplateswithnumerouscontent

    classes,including:PhotoCarousel,RSSFeed,Calendar,Video,Tabs,Accordions,Blog,Forms,GoogleMaps,PersonBios,Newsarticles,andnumeroustextentryoptions.http://demo.wiscwebcms.wisc.edu/,http://demo.wiscwebcms.wisc.edu/responsive/

    Templateshaveaccessibilitybuiltin. NewcustomtemplatesaredevelopedbytheWiscWebCMSteamasneeded.

    Includesacustomizableworkflow,withapprovalbeforepublishing Templatesalloweasyeditingbycontentowners,reducingtheneedforweb

    developerstoupdatecontent.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 13 of 23

    http://info.wiscwebcms.wisc.edu/http://demo.wiscwebcms.wisc.edu/http://demo.wiscwebcms.wisc.edu/responsive/http://demo.wiscwebcms.wisc.edu/responsive/

  • Templatesallowextremeflexibility,allowingwebdeveloperstocombinecomplexwebappswithcontentthatisupdatedbycontentowners.

    Providesversioning,withcompareversions,andrestoreversion Contentcanbeactivated/deactivatedautomaticallyatpredeterminedtimes. OriginalRedDOTCMSwasselectedbyanexhaustiveRFPprocess,and

    includedacampuswideteamofusers/serveradminsthatreviewedover15differentCMS's.

    DoITHosting #Sites:215WordPress,40Drupal,someSilverstripe&Joomla #staff:? #infrastructurecost(licenses&hardware):? Service(noninfrastructure)cost:? Costtouser:$0ifhtmlonlysitewith5GBstorage,thenthreetiersfordatabase(ie

    WordPress)withmultidomains,startingat$45andanenterpriserestricteddatahostingfor$150/month.NOTE:basicWordPress/Drupalis$540/year.

    ServiceNarrativeTheservicehasalltheusualoptionsunlimitedbandwidth,nightlybackups,abilitytoincreasequota,usagereporting,test/prodservers,andcustomdomains(mysite.wisc.edu).TheysupportopensourceapplicationsthroughPleskSupportControlPanelwhichisgreatforquicklycreatingsites.EasyintegrationwithNetIDandpartnershipswithDoITADIandWiscWebCMS.Theytakecareofpatchingthecoreservice,howeverthingslikeWordPresspluginsneedadditionalmanualattention.Thehaveadditionalsecurity,includingMod_securitythathelpsmoderateconnectionstotheserverpreventingsomekindsofattacks,adminfeaturesonlyavailableoncampusorthroughVPN.Serviceisfocusedonempoweringuserswiththeaccesstothekindofservertheyneed,quickly,andwithselfserviceoptionstoquicklybeupandrunningwithareliablehost.Theyhaverapidsupportresponsewhenneeded.Theserviceissuitableforanyonefromastaticdreamweaverwebsite(free),toacomplexDrupal/WordPresssite(atamonthlyfee),orrestricteddata(atamonthlyfee,seeabove).DesignandDevelopmentisavailableatanhourlyrate.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 14 of 23

  • SampleDrupalHostinginChemistry #Sites:around75 #staff:.5FTE,.2studenthourly

    representingthefollowingroles: Project Manager, Application Administrator, Support Consultant, Application Developers, Database Administrator, End User and Administrator Trainers, System Administrator, LDAP Administrator

    #infrastructurecost(licenseandhardware):$4,000 Service(noninfrastructure)cost:$0 costtouser:$0

    ServiceNarrative

    ProvideDrupalCMSforanydepartmententitythatislookingforawebpresence.AllhardwareinfrastructureishostedatChemistry.Thisincludes70+sitesincludingthemaindepartmentsite,researchgroupwebsites,events,facilitiesandinventorydatabases.Thesesitesthatwesetupinitiallyarethenhandedovertothosegroupsthatweworkalongside.Thiscanbegraduatestudents,staff,orfaculty.Weoffermultipletemplatesandtailorthesitestotheneedsoftheuser/group.AresearchgroupUWbrandedthemedsiteisalreadyinproductioninChemistry.Ourserviceofferingiscomprisedofateamof3people.

    AdminTheadminisinchargeofsecurity,patchingtheapplicationandsystem,andinitialdrupalinstall.Thisishandlebyoneperson.

    DevelopmentThesupportteamincludesflushesoutwhatthemaindepartmentwebsitewilllooklikeandhowitwillfunction.Theyarealsoworkdirectlywithentitieswhoarelookingforanewwebsite.Theycollectinformationabouthowtheuserwouldlikethesitetooperate.Thisdutyishandledby3ofus.Twopeopleoftheteamcanhandlethebasicdevelopment.Ifitcomplicated,the1maindeveloperwillstepintohelp.

    SupportAnyquestionsaboutaddingcontent,addingnewfunctionalityalsogoesthroughourthreeteammembersfortriage.Trainingandsupportisdoneinpersonandviaemailwheneverusershavequestions.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 15 of 23

  • SampleDrupalHostinginLSS #Sites:133 #staff:1FTE

    representingthefollowingroles: Project Manager, Application Administrator, Support Consultant, Application Developers, Database Administrator, End User and Administrator Trainers, System Administrator

    #infrastructurecost(licenseandhardware):$1300/yfortwovirtualservers,2serverspurchasedat~$6k(approximately$1,000peryear)

    Service(noninfrastructure)cost:$0 costtouser:$0

    ServiceNarrative

    SimilartoChemistry,mostsupportinoneperson,withsomedutiessupplementedbyothers.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 16 of 23

  • CMSAssessmentSurveyResponsesSummary

    1. Whocompletedthesurvey?a. Mostresponsesfromstaff(86%)b. Mostrespondentsaredecisionmakers(84%)c. Almostallrespondentsareaffiliatedwithawebsite(97%)d. Majorityofrespondentshavecontentrelateddutieseditor,publisher,reviewer

    (65%)andwriter/contributor(59%).e. RoughlyonethirdofrespondentsidentifiedasITprofessional,siteadministrator,

    systemadminandanotheronethirdidentifiedasDesigners.f. Only16%identifiedasDeveloperorprogrammer.g. Exactly27respondentsidentifiedasDean/CIO/ExecutiveAdministrator.

    2. Whatdidwelearnaboutthewebsitesrepresentedinthesurvey?

    a. Almostallwebsiterepresentedinthesurveyarepublicfacingwebsites(92%)b. Othersignificantfunctionsincludeintranet(35%),events/eventrelated(54%),

    andpersonal/biographical/researchrelated(30%)c. Anumberofrespondentsusedtheotherfunctionsfieldtoaddacommentabout

    thedesireforwebbasedforms,scheduling,orotherdatainputtypefunctions.d. Ofthewebsitesrepresentedinoursurvey,approximately70%havebeenonthe

    currentplatformformorethantwoyears.

    3. Approximately144respondents(30%)indicatedthatthewebsitesrepresentedinthesurveyhavebeenonthecurrentplatformforlessthantwoyears.Whatdidwelearnaboutthesewebsitesandassociatedrespondents,inparticular?

    a. ThemostcommonpriorplatformresponseistheHTML/CSS(e.g.Dreamweaver)selection.SincethecommitteeoptedtocombineHTML/CSSwithDreamweaver,wecantbesurehowmanyofthesepriorplatformswerehandcodedwebsitesasopposedtoDreamweaverwebsites.

    b. ThesecondhighestnumberofresponsesforpriorplatformisWiscWebCMSwith28responses(20%).

    c. Oftheotherresponsesforquestion11(Whatwaspriorplatform?),therewereonlythreeuniqueplatformscitedwithmorethan2responseseach:AdobeContribute,Sitefinity,andJoomla.

    d. Ofthereasonscitedforleavingthepreviousplatform,costhadthelowestresponseofallreasonsprovided(6%)

    e. Ofthereasonscitedforleavingthepreviousplatform,dissatisfactionwithfunctionalityreceivedthehighestnumberofresponses(54%)

    f. Dissatisfactionwithtechnicalsupportofferings(37%)andplatformmaintenanceconcerns(38%)bothreceivedsignificantresponses

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 17 of 23

  • g. Twocommonthemesemergedinthecommentsforquestion12(Whydidyouleaveyourpriorplatform?).Thefirstthemeconcernedtheavailabilityofandeaseofaccesstoasetofprebuilt,UWbrandeddesigns/templatesonotherplatforms.Thesecondcommonthemedetailedanunacceptablyhighlevelofperceiveddifficultyforbasiccontenteditingoperationsonthepriorplatform.

    h. Aswouldbeexpectedtheprioritiesintheselectionofthenew/currentplatformmirrorthereasonsforleavingtheoldplatform.Thesamethreeselections:functionality,technicalsupport,andplatformmaintenanceeachhadover50%response.

    i. Thesame(inverse)themesweretrueofthecommentsforquestion13(Whatwereprioritiesinselectionofcurrent/newplatform?).Commonthemesincluded:easeofuseforcontentediting,availabilityofcommonUWthemedbrandingcomponents,andtheavailabilityoflocaltechnicalsupportoptionsfortheplatform.

    j. Interestingly,whilethecostoptionwasnotselectedasasignificantconcernwiththeoldplatform(6%)norasignificantpriorityforthenew/currentplatform(3%),itdidemergefrequentlyinthecommentsfortheprioritiesfornewplatform(question13).Approximately30%ofthecommentsincludedatleastonereferencetolowcostorfreeasbeinganimportantconsiderationintheselectionofthenewplatform.Thecostoptioninquestion13waslabeledasdissatisfiedwiththecostandIthinkthatmighthavecausedsomeconfusionforrespondents.

    4. WhatCMSsystemshaverespondentsused(question15)?a. Outof499responsesintotal,185respondentshaveusedWiscWebCMS(37%),

    295respondentshaveusedWordPress(59%),and144respondentshaveusedDrupal(29%).Additionally,61%ofrespondentshaveusedHTML/CSS(e.g.Dreamweaver).Asnotedabove,duetothespecificsurveylanguageused,wecannotdifferentiatebetweenmanualHTML/CSScodingandDreamweaverusage.

    b. Otherwasselectedby111respondents(22%).Otherplatformsmentionedatleast3timesincludeJoomla(13),Sitefinity(6),DotNetNuke(5),AdobeContribute(4),ExpressionEngine(3).

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 18 of 23

  • 5. WhatCMSsystemsarerespondentsusingnowtomanagetheirwebsitesandhowmanywebsitesaretheymanagingoneachCMS(question16)?

    CMS Response %Resonse Websites %ofTotal

    WiscWebCMS 145 33% 175 9%

    WordPress 201 45% 658 34%

    Drupal 80 18% 260 14%

    HTML/CSS 144 33% 338 18%

    SharePoint 15 3% 17 1%

    GoogleSites 37 8% 78 4%

    Other1 72 16% 277 14%

    Other2 11 2% 118 6%

    6. ArerespondentssatisfiedordissatisfiedwiththeCMSsystemstheyareusingnow?Thisisasummaryofthedatacollectedinquestions17,18,and19.Forthepurposesofasummary,wehavecombinedVerySatisfiedandSatisfiedintooneresponseandVeryDissatisfiedandDissatisfiedintooneresponse.

    CMS Functionality Support Maintenance

    %Sat.

    %Dis. %Sat.

    %Dis. %Sat.

    %Dis.

    WiscWebCMS 40 33 54 16 47 15

    WordPress 72 4 45 16 59 8

    Drupal 42 12 34 17 34 19

    HTML/CSS/DW 50 20 41 19 41 25

    SharePoint 15 19 10 21 11 16

    GoogleSites 43 9 28 16 29 12

    Other1 49 15 27 24 37 22

    Other2 19 10 14 9 19 10

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 19 of 23

  • 7. Whatisyouraffiliationtotheuniversity?(chooseone)

    Affiliation Count %

    Staff 517 86.5%

    Faculty 46 7.7%

    Undergraduatestudent 7 1.2%

    Graduatestudent 9 1.5%

    Postdoctoral 0 0%

    PA/TA 1 0.2%

    Other 18 3.0%

    8. Areyouadecisionmakerregardingyourgroupswebsite?(chooseone)

    DecisionMaker Count %

    Yes 312 52.2%

    No 100 16.7%

    No,butmyrecommendationwillbeaccepted. 186 31.1%

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 20 of 23

  • 9. Whatrole(s)doyouplayinthemanagementofyourgroupswebsite?(selectallthatapply)

    Role Count %

    Campuscommunicatorormarketing 152 28.8%

    Webeditor,publisher,orreviewer 342 64.7%

    ITprofessional,siteadmin/custodian,accountmanager,servermaintenance

    140 26.5%

    Contentcontributor,copywriter 313 59.3%

    Owner 118 22.4%

    Designerorlayouteditor 170 32.2%

    Developerorprogrammer 87 16.5%

    Dean/CIO/ExecutiveAdministrator 27 5.1%

    Other 52 9.9%

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 21 of 23

  • 10.PeoplewhohaveWiscWebCMSsites,andareplanningonanewsiteinthenexttwoyears.

    11.PeoplewhohaveWordPresssites,andareplanningonanewsiteinthenexttwoyears.

    12.PeoplewhohaveDrupalsites,andareplanningonanewsiteinthenexttwoyears.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 22 of 23

  • WiscWebCMSsatisfactionresultsforpeoplewithWiscWebCMSsites.

    WordPresssatisfactionresultsforpeoplewithWordPresssites.

    DrupalsatisfactionresultsforpeoplewithDrupalsites.

    Appendix 1 - CMS Assessment Committee - Findings and Assessment

    Page 23 of 23

  • Printed11/17/2015

    CMS Assessment Committee Phase I Report Appendix 2 CMS Assessment Committee Survey Results Without Comments

  • CMS Assessment Committee - Survey

    Full Report, without individual comments

    11/12/2015

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 1 of 23

  • 1 517 86.45%

    2 46 7.69%

    3 7 1.17%

    4 9 1.51%

    5 0 0.00%

    6 1 0.17%

    7 18 3.01%

    598 100.00%

    # Answer Bar Response %

    Staff

    Faculty

    Undergraduate student

    Graduate Student

    Postdoctoral

    PA/TA

    Other

    Total

    What is your affiliation to the university? (choose one)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 2 of 23

  • 1 312 52.17%

    2 100 16.72%

    3 186 31.10%

    598 100.00%

    # Answer Bar Response %

    Yes

    No

    No, but my recommendation will beaccepted.

    Total

    Are you a "decision maker" regarding your group's website? (choose one)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 3 of 23

  • 1 596 97.23%

    2 17 2.77%

    613 100.00%

    # Answer Bar Response %

    Yes

    No

    Total

    Does your university group currently have a website? (choose one)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 4 of 23

  • 1 7 41.18%

    2 10 58.82%

    17 100.00%

    # Answer Bar Response %

    Yes

    No

    Total

    Is your university group currently pursuing the creation or development of a website?

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 5 of 23

  • 1 3 60.00%

    2 1 20.00%

    3 3 60.00%

    4 0 0.00%

    5 0 0.00%

    6 3 60.00%

    7 1 20.00%

    8 1 20.00%

    12 100.00%

    # Answer Bar Response %

    an intranet (sharing documents,information inside our organization, etc.)

    instructional/educational content(information aimed at students, a site thatstudents contribute content to, etc.)

    to share information with the public aboutour organization (college, school,department, program, center, institute,lab, research center, etc.)

    personal/biographical/research related (aprofessor's CV, a "research notes" blog,etc.)

    cultural/heritage/online exhibits

    events/event-related

    Student organization

    Other:

    Total

    What functions do you envision being served by your group's website(s)? (select all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 6 of 23

  • 1 1 20.00%

    2 5 100.00%

    3 1 20.00%

    4 2 40.00%

    5 0 0.00%

    6 3 60.00%

    7 0 0.00%

    8 0 0.00%

    9 1 20.00%

    13 100.00%

    # Answer Bar Response %

    WiscWeb

    WordPress

    Drupal

    HTML/CSS (e.g. Dreamweaver)

    SharePoint

    GoogleSites

    None

    Other

    Comments:

    Total

    Below is a list of web content management platforms or tools. Please, indicate any that you or your group hasexperience working with. Use the "Comments" field to elaborate. (choose all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 7 of 23

  • 1 5 100.00%

    2 1 20.00%

    3 3 60.00%

    4 1 20.00%

    5 0 0.00%

    6 0 0.00%

    10 100.00%

    # Answer Bar Response %

    functionality (e.g. the ability to create newpages, edit existing pages, make minorchanges to appearance and layout)

    technical support (e.g. the ability todevelop new features, expand thewebsite's usefulness)

    maintenance (e.g. maintaining versions,installing patches, managing backups,security, etc.)

    dissatisfied with the cost

    I don't know

    Comments:

    Total

    What will be your priorities when selecting a platform? Use the "Comments" field to elaborate. (select all thatapply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 8 of 23

  • 1 152 28.79%

    2 342 64.77%

    3 140 26.52%

    4 313 59.28%

    5 118 22.35%

    6 170 32.20%

    7 87 16.48%

    8 27 5.11%

    9 52 9.85%

    1401 100.00%

    # Answer Bar Response %

    Campus communicator or marketing

    Web editor, publisher, or reviewer

    IT professional, siteadministrator/custodian, accountmanager, or server maintenance

    Content contributor, copy writer

    Owner

    Designer or layout editor

    Developer or programmer

    Dean/CIO/Executive Administrator

    Other:

    Total

    What role(s) do you play in the management of your group's website (select all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 9 of 23

  • 1 194 35.79%

    2 246 45.39%

    3 498 91.88%

    4 161 29.70%

    5 42 7.75%

    6 292 53.87%

    7 54 9.96%

    8 61 11.25%

    1548 100.00%

    # Answer Bar Response %

    an intranet (sharing documents,information inside our organization, etc.)

    instructional/educational content(information aimed at students, a site thatstudents contribute content to, etc.)

    to share information with the public aboutour organization (college, school,department, program, center, institute,lab, research center, etc.)

    personal/biographical/research related (aprofessor's CV, a "research notes" blog,etc.)

    cultural/heritage/online exhibits

    events/event-related

    Student organization

    Other:

    Total

    What is the function served by your group's website(s)? (select all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 10 of 23

  • 1 158 28.52%

    2 182 32.85%

    3 149 26.90%

    4 65 11.73%

    554 100.00%

    # Answer Bar Response %

    less than 2 years

    2 to 5 years

    6 or more years

    I don't know

    Total

    How long has your group's current website existed on its current platform? (choose one)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 11 of 23

  • 1 28 19.44%

    2 22 15.28%

    3 11 7.64%

    4 44 30.56%

    5 0 0.00%

    6 2 1.39%

    7 40 27.78%

    8 28 19.44%

    175 100.00%

    # Answer Bar Response %

    WiscWeb

    WordPress

    Drupal

    HTML/CSS (e.g. Dreamweaver)

    SharePoint

    GoogleSites

    Other

    Comments:

    Total

    You indicated that your group's current website is less than two years old. On which of the following platforms ortools was your group's website built prior to the current platform? Use the "Comments" field to elaborate. (selectall that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 12 of 23

  • 1 78 54.17%

    2 54 37.50%

    3 55 38.19%

    4 8 5.56%

    5 34 23.61%

    6 61 42.36%

    290 100.00%

    # Answer Bar Response %

    dissatisfied with the functionality (e.g. theability to create new pages, edit existingpages, make minor changes toappearance and layout)

    dissatisfied with the technical support (e.g.the ability to develop new features,expand the website's usefulness)

    dissatisfied with maintenance (e.g.maintaining versions, installing patches,managing backups, security, etc.)

    dissatisfied with the cost

    I don't know

    Comments:

    Total

    Why did your group migrate from the prior platform(s)? Use the "Comments" field to elaborate. (select all thatapply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 13 of 23

  • 1 106 72.60%

    2 77 52.74%

    3 75 51.37%

    4 4 2.74%

    5 25 17.12%

    6 41 28.08%

    328 100.00%

    # Answer Bar Response %

    functionality (e.g. the ability to create newpages, edit existing pages, make minorchanges to appearance and layout)

    technical support (e.g. the ability todevelop new features, expand thewebsite's usefulness)

    maintenance (e.g. maintaining versions,installing patches, managing backups,security, etc.)

    dissatisfied with the cost

    I don't know

    Comments:

    Total

    What were your priorities when selecting the current platform? Use the "Comments" field to elaborate. (select allthat apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 14 of 23

  • Ease of use was big as we do not have a dedicated web dev.

    From what I understand the old version of DNN was not going to work any longer on a server so we had to bemoved over to the new version.

    We were extremely happy and impressed with the support and professionalism of Learning Support Servicesthrough L&S.

    cost is a major factor. we need to take advantage of campus resources that are affordable.

    We chose WiscWeb so we could easily and cheaply create a website for our department. I was what was availablenon cmapus to use for free.

    Support from WiscWebCMS staff to migrate our site (at no cost) was extremely attractive when choosing a newplatform.

    WiscWeb CMS was presented and understood to be the platform of choice for the enterprise.

    There was no website before I started working here. I started one. I asked someone and they told me how to startone. I really didnt choose, didnt know there were other options.

    Align with the campus standard.

    We chose WiscWeb to conform to the University's "look" and to have DoIT support and training.

    View More

    Text Entry

    (Optional) Please, elaborate with any other relevant details as to why the current platform chosen.

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 15 of 23

  • 1 188 36.72%

    2 301 58.79%

    3 148 28.91%

    4 315 61.52%

    5 48 9.38%

    6 103 20.12%

    7 22 4.30%

    8 112 21.88%

    9 51 9.96%

    1288 100.00%

    # Answer Bar Response %

    WiscWeb

    WordPress

    Drupal

    HTML/CSS (e.g. Dreamweaver)

    SharePoint

    GoogleSites

    None

    Other

    Comments:

    Total

    We would like to know what content management platforms or tools you have used anywhere, not limited to yourcurrent website. Please, check all the relevant items below. Use the "Comments" field to elaborate. (select all thatapply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 16 of 23

  • 1 147 32.59%

    2 204 45.23%

    3 83 18.40%

    4 147 32.59%

    5 15 3.33%

    6 37 8.20%

    7 73 16.19%

    8 11 2.44%

    9 63 13.97%

    780 100.00%

    # Answer Bar Response %

    WiscWeb

    WordPress

    Drupal

    HTML/CSS (e.g. Dreamweaver)

    SharePoint

    GoogleSites

    Other1

    Other2

    Comments:

    Total

    Please, tell us about your current web environment. Some groups on campus are responsible for multiple websites.Indicate the approximate number of websites in your group that are managed on the various platforms. Use the"Comments" field to elaborate. (select all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 17 of 23

  • 1 WiscWeb 223 2.91

    2 WordPress - 269 2.12

    3 Drupal 160 2.61

    4 HTML/CSS (e.g.DreamWeaver) 220 2.56

    5 SharePoint 79 3.10

    6 GoogleSites 99 2.56

    7 Other1 74 2.51

    8 Other2 21 2.90

    # Question VerySatisfied Satisfied Neutral DissatisfiedVery

    Dissatisfied ResponseAverage

    Value

    29 60 61 49 24

    54 139 65 11

    22 45 73 14 6

    37 73 67 35 8

    2 10 52 8 7

    13 29 48 7 2

    14 22 27 8 3

    1 3 15 1 1

    Where applicable, indicate your group's satisfaction with the functionality of the following web contentmanagement platforms or tools.

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 18 of 23

  • 1 WiscWeb 204 2.45

    2 WordPress 239 2.62

    3 Drupal 144 2.77

    4 HTML/CSS (e.g.DreamWeaver) 181 2.68

    5 SharePoint 64 3.14

    6 GoogleSites 84 2.85

    7 Other1 67 2.91

    8 Other2 22 2.95

    # Question VerySatisfied Satisfied Neutral DissatisfiedVery

    Dissatisfied ResponseAverage

    Value

    44 66 61 24 9

    28 80 92 32 7

    16 32 71 19 6

    26 49 72 25 9

    2 4 45 9 4

    6 17 48 10 3

    9 9 33 11 5

    1 2 17 1 1

    Where applicable, indicate your group's satisfaction with the technical support available with the following webcontent management platforms or tools.

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 19 of 23

  • 1 WiscWeb 206 2.57

    2 WordPress 245 2.39

    3 Drupal 144 2.83

    4 HTML/CSS (e.g.DreamWeaver) 180 2.82

    5 SharePoint 65 3.09

    6 GoogleSites 84 2.81

    7 Other1 63 2.83

    8 Other2 21 2.90

    # Question VerySatisfied Satisfied Neutral DissatisfiedVery

    Dissatisfied ResponseAverage

    Value

    36 62 77 17 14

    34 109 81 14 7

    12 36 68 20 8

    21 53 61 28 17

    1 6 48 6 4

    5 19 50 7 3

    7 16 26 9 5

    1 3 15 1 1

    Where applicable, indicate your group's satisfaction with the maintenance involved with the following web contentmanagement platforms or tools.

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 20 of 23

  • 1 157 32.44%

    2 327 67.56%

    484 100.00%

    # Answer Bar Response %

    Yes

    No

    Total

    Is your group considering migrating to a new platform in the next two years?

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 21 of 23

  • 1 26 18.31%

    2 88 61.97%

    3 23 16.20%

    4 9 6.34%

    5 3 2.11%

    6 5 3.52%

    7 2 1.41%

    8 42 29.58%

    198 100.00%

    # Answer Bar Response %

    WiscWeb

    WordPress

    Drupal

    HTML/CSS (e.g. Dreamweaver)

    SharePoint

    GoogleSites

    None

    Other

    Total

    You indicated your group is considering a migration to a new web content management platform. Below is a list ofweb content management platforms or tools. Please, indicate any that your group is considering for this migrating.(select all that apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 22 of 23

  • 1 131 88.51%

    2 92 62.16%

    3 102 68.92%

    4 8 5.41%

    5 12 8.11%

    6 48 32.43%

    393 100.00%

    # Answer Bar Response %

    functionality (e.g. the ability to create newpages, edit existing pages, make minorchanges to appearance and layout)

    technical support (e.g. the ability todevelop new features, expand thewebsite's usefulness)

    maintenance (e.g. maintaining versions,installing patches, managing backups,security, etc.)

    dissatisfied with the cost

    I don't know

    Comments:

    Total

    What will be your priorities when selecting the next platform? Use the "Comments" field to elaborate. (select allthat apply)

    Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments

    Appendix 2 - Page 23 of 23

  • Printed11/17/2015

    CMS Assessment Committee Phase I Report Appendix 3 CMS Assessment Committee Survey Results Comments Only

  • Q2_TEXTWhatisyouraffiliationtotheuniversity?(chooseone)Workedonwebsiteasagraduatestudent;nowinaninterimacademicstaffposition.ProfessorEmeritusContractor(Webwork)Outreachspecialist,UWExtension,fundedthroughCALSProfessionalOrganizationVolunteerstaffandstudent(multiplerolestherearesomeofus)contractorStudentWebDeveloper(workstudystaff),undergraduateUWHospitalemployeeMarketingPartner/VendorEmeritusVendorEmeritaprofessorEmeritusProfessor

    Q8_9_TEXTWhatrole(s)doyouplayinthemanagementofyourgroup'swebsite?(Selectallthatapply)AdvisorandUnitDirector

    assistantdeanresponsibleforcommunications,ourteamisjustme,oneotherpersonandahandfulofstudentsContentreviewer/approverCoordinator(orDirector)ofthreeprogramswiththreeseparatewebsites.coownerwithprogramdirectordepartmentadministratoranddevelopmentcommitteememberDepartmentSupervisorDeveloperformanyothercampusunits,frequentlyreferpeopletosharedhostingDirectorofWebsiteServicesDirector;Chairdivisional/pathcoordinator,IdoedittwowebsitesalsoDon'tplayarolefacultydirectorGiveinputonsitecontentasastaffmemberIcreateinformationthatgetspostedontheWebpageregardingourprogramIeditandmanageasitewithinalargergroup'swork.Ihavebeeninmarketing,editing,designer,anddeveloperroles.CurrentlyIsupervisethosewhodothesefunctions.Imaintainmyownwebsitebecauseitistoohardtoupdateourgroup's

    Ipostinformatiionabouteventsandfielddayshappeningatourstationanddata/resultsfromdisplaygardenIprovidecampuswideservices(EOHdept)OccupationalHealthIsupervisetheemployeewhodevelops,designs,andmaintainsit.I'madigitalprojectmanageratalocaladagency.Liaisontowebdeveloper

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 1 of 44

  • Manager,technologygroupManagingdatafromourFilemakersystemtoanOraclesystemwhichthenfeedsourCMSn/anaNoroleNorollatallnonenonenoneNotallowedtomanageourwebsite.Cangiveinput/advice,butrarelylistenedto.ourgroupwebsitehasasetofpagesassignedtothesubunitImanageprovideinputandfeedbacktoassistwithdesignandcontentinformationReview/RecommendwebsiteinterfacewithourmanagementtrackingdatabasesystemSEOconsultantSomecontentneedstobeapprovedbyme;anyexpenditureshavetobeapprovedbymeStrategicplanningforunitsuppliespurchasing,includingsogftwareiftheorderisapprovedThesearepositionsfromthepreviousacademicyear.Iremainaresourcewithsomeauthority.Twowebsites:oneformyresearchgroup,oneformydepartment(Iamthechair)updatesUserwillbeacontributor

    Q19_8_TEXTWhatisthefunctionservedbyyourgroup'swebsite(s)?(selectallthatapply)Other:Alloftheselectedabovearerepresentativeofourclients.Ourgroupalsohasitsowninformationalsite.alsotoshareinternallyinformationaboutpolicies,etc.aninfrastructureformanygroupsofresearchspecificresourcesApplicationheavyassistpeopletoidentifyandrequestservicesfromthegroupChildcarebusiness,labschool(research&teaching)CommunicateaboutourorganizationsservicestocampuspatronsCommunicatewithfaculty,staff,studentsandalumniContentaimedatotherUWMadisonusers(administrators,staff,faculty)contentdistribution(filesinexcel,pdf,etc.)datareportingforpublic/student/staff/factultyDocumentationfortechnologywehavethattheUWMadisoncommunitycanuse.educationalcontentfortheindustrywesupport(nontraditionalstudents);shortcourseregistration;

    helpstudentsapplyandenroll;providepolicyinfoforstudents;provideresourcesforstudentsandcommunityhttp://snapplus.wisc.edu/WisconsinNutrientManagementsoftwaresiteindustryoutreachInformationandgatewayonhowtouseservicesforstudents;resourceforfacultyinformationforstudents(buttheydon'tcontribute)Informationonprogramsincludingapplicationlinks.informationtargetedtophysicians,researchers,andadvancedpractitionersinacademicmedicine

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 2 of 44

  • Instructionalcontentaimedatadultlearners,particularlyfarmers;instructionalcontentaimedathighschoolaginstructorsInstructionalcontentaimedatemployesslargecampuswideinitiativeMarketingtorecruitstudentstoourprogramsMyorganizationhasbuiltalloftheaboveforcampusorganizations.Office365informationandtrainingforemployeesOnBoarding,HR,andPayrollbothInternallyandExternallyOrganizationalrecruitmentOurwebsiteaddressesfaculty,staffandstudentissuesacrosscampusfromdriverauthorizationtoapprovedvendors.personalProgramregistrationProvideresearcherswithknowledgeofourservices,webformsforselectingthoseservices,arepositoryforvariesprintedreportsandformsandassistancewiththefundingprocess.Providingcentrallocationforstudentleadergrouporganization,providingcentrallocationforstafforganization(multiplesites)publicizeeventsandprogramsofmultipleentitiesacrosscampusRealtimeweatherdatarequestformsResearchsupportresourcesneededbyfaculty,universityguidanceschedulingappointmentsSellUWPressbooksthroughourwebsiteandprovideinformationaboutthePress(esptoauthors)Sellingcoursesbothnoncreditandcredit.shareinformationandresourceswithmembersshareinformationwithfacultyaboutgovernanceactivities,mostlyoncampusshareopportunitiesforgrantfunding,distributeresearchpolicysoftwareassurancefacilitystreamingStudentJobCenterjobceter.wisc.edubuiltforcampusbutusedbyMadisoncommunityalso.Wiscidea,inaction.technicaltrainingandorganizationinformationThissitesharesacademicinformationsuchasdegreerequirementsbothonandoffcampus.tocommunicatewithUniversityandcommercialclients/researcherstoinformpatronsaboutourservicesTomakecertainkindsofdatamorevisibleandvisual,andtomakeiteasiertoaccessthatdata.toshareinformationwithcriticalaccesshospitals,clinics,nurses,hospitaladministrators,etc.VariousFunctionalGroupSpecificApplicationswewouldliketoaddintranetbuthavenotbeenabletomustertherequiredresourcestodothatWebaccesstoourprofessionaldevelopmentcatalogWebHosting,CMSmanagement,WebDevelopment

    Q14_7_TEXTYouindicatedthatyourgroup'scurrentwebsiteislessthantwoyearsold.Onwhichofthefollowingplatformsortoolswasyourgroup'swebsitebuiltpriortothecurrentplatform?Other

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 3 of 44

  • AngularJSCMSRedDotContributeContributeContributeCustomASP.netCMSCustombuiltCMSDIY/handcodedDNNDotNetNukeolderversionDon'tknow.SiteishostedondepartmentsWebsitedon'tknowDont'knowwhatitwasbeforemigrationtoWiscWeb1.5yearsagothemigrationto"current"wiscwebsiteoccurredbeforemytenure.Wearerevampingcurrentlayoutandcontentofwebsitenowusingwiscwebasitdoesnotfitourneeds.dotCMSDotNetNuke7DreamweaverDreamweaverDreamweaver,alongwithacustomdevelopeduploadandversioningsystemEMS?HomegrownCMSdevelopedinternallyHomegrownwithHtml,javaandPhpIamnotsureIthinkitwasDreamweaver,butI'mnotsureJoomlaJoomlaJoomlajoomlaN/ANotsurenotsurenotsure,UHSIT/commuicationscanaddressthisquestionw/yourgroupSilverStripeSitefinitysitefinityTherewasnone.UnknownWebservicesconsumedbyWordPressfordatadisplay,e.g.Libraryhoursandservices,staffdirectory,etc.

    Q14_8_TEXTYouindicatedthatyourgroup'scurrentwebsiteislessthantwoyearsold.Onwhichofthefollowingplatformsortoolswasyourgroup'swebsitebuiltpriortothecurrentplatform?Commentsbuiltandmaintainedentirelyinhouse,withsporadicstudentdeveloperassistanceCurrentlyWordPress,donotrecallwhatitwasbefore,possiblywiscwebdon'tknow

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 4 of 44

  • dotCMSwasfreewhenweswitchedtoit.BeforethenwehadIBMWebSphere,whichwasexpensiveandverydifficulttouse.HaveconsolidatedthemultipleprogramsinourofficeoverthepastfewyearsinanattempttohaveallaffiliatedwebsiteshostedinWiscWebCMSIamnotsure.WeupgradedtoDNN7andIamnotsurewhatitwaspriortothat.IbelieveitwasHTML,butthemainofficesiteisDrupalIdonotknowIdon'tknow,asIjuststartedthispositionineraly2015.Idon'tknow,butmyguessisHTML/CSSIdon'tknow;websitewasdesignedbyourPA;wehadtoswitchtoDrupalIshouldclarifythatwewereonWiscWebpriortonow,butin20132014weupdatedtothestandardtemplates.PriortothatthewebsitewasbeingdoneinDreamweaver.Iwasn'taroundyet.newsitetoreplacecrappyoldsite.CMShasbeengood

    NotsureifthatwasthenameoftheplatformbutthatwastheprogramIusedtomakechangestothewebsite.Notsure.Notsure.Wasnotresponsibleforitatthattime.notsure;wasnotemployedhereatthattimeOurmainsiteisbasedonacustomASP.netsolution.OursisWordPress.WeoftendoDrupalworkaswell.Stillsupportsitefinityforotherinstances

    Unitandwebsitesdidnotexistpriortocurrentplatformthesearenewresourcesforstudentsandforfacstaff.WeboughtserverspacefromDoIT.WedidnothaveawebsiteWemovedthesitefromD6toD7.Doesthatcountasmovingplatforms?wenowhaveWordpressbutIdon'trememberwhatitwasbeforethatbecauseCALSITmanageditthenWerecentlymigratedtoWiscWebCMSafterourDrupalsitewashacked.websitewasnewlylaunched,didnothaveapriorlife

    Q15_6_TEXTWhydidyourgroupmigratefromthepriorplatform(s)?Comments:alsowiththeinabilitytocontrolvarioususerrightsBiggestreasonwastheresponsivedesignofferedbyWWCMS.SecondaryreasonsincludedbetternavigationandadaptingacloserreplicationoftheUWbrand.CALSARSasagroupmovedfromtheContributeplatformtoWordpressCALSmadethedecisiontomovefromAdobeContributetoWordPress.Didn'tmigratestartednewsitewithWiscWebCMS.dissatisfiedwithcomplexityofsimpletasksANDdifficultyofimplementinglargercustomfunctionalitydissatisfiedwiththespeedofimplementationandtheflexibility.WiscWebwasunknowntomanyoutsidedeveloperssowecouldn'tengageexternalresourcestosupportit.Dreamweaveristerrible.drupalwassoclumsyEasiertohavestafftrainedinasingleplatform.Additionally,DoITsupportandfreeclassesforbeginnertrainingweahugeplus

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 5 of 44

  • FoundWiscWebnottobeuserfriendlyforpeoplemaintainingthesite.Overlycomplicatedandnotintuitiveatall,andonlinedocumentationislacking.GroupwearepartofallmigratedtoWordpress.Havedeveloperswhocoulddoworkbuttimewasscarceforthat,wantedtomovetoaplatformthatallowedmore,lesstechnical,contributorstowebsiteupdatesandmanagementIdon'trememberbutIbelieveithadtodowithnotbeinglookingcurrentenough(layout,design,functionality)andpossiblynotmobilefriendlyIwasnotresponsibleforthemigrationchoice,andwasfinewiththeoldersystem.IwasverysatisfiedwithDreamweaver,butourDirectorwantedustohaveawebsitethatutlizestheUWThemeinWordpress.ItwasmoretohavesomethingmorecompatiblewithCALSandtohavesomethingthatworkedbetter.Itwasmoreaboutmovingforwardthatdissatisfaction.LaunchedanewUWbrandedwebsitewithassistancefromUWCommunicationsLSSrequiredtheswitchforsecurityreasons.OursitewasbreachableandprovidedawayintoothersystemsforhackersMeatSciencewascoveredbyAnimalScienceWebsite,nowwehaveonefornewfacilityconstructionupdates.//Bucky'sButcherywasalsothroughtheDepartmentofAnimalScience.Wewereunabletoaccessandeditthecontent,sowewentaboutgettingourownsite.MovedfromastaticHTML/CSSsitemaintainedusingDreamweavertoadynamicCMSMovedtowiscwebCMStobetteralignwithothercampusunits,alsoforthesupportproviededbyDoItandtheeaseofuseofthetool.Mywebsiteishostedbyanothergroupthatmadetheplatformchoice.N/ANeededsomethingmorerobust,easiertouseandmaintainfornondevelopers,contemporarydesignandfunctionality.Newsite.didn'tmigrateNolongerwasfree.nomigration,thiswasjuststarted.oldfashionedlookandfunctionalityofthesite;manychangeswithinourofficeandsomuchneededupdating,itwasagoodopportunitytogowiththeresponsivedesignwiscwebcmsOurcontactendedwithoneproviderandthenewproviderwasselectedbasedoffapriorcontractualrelationship.Previouscmswascumbersomeforendusercontentproviders.previousversionwasmaintainedbysinglepersonindepartmentifpersonwasunavailableorunwillingtoupdate,nootherscouldcontributeRatherthanupgradeownunit'ssitetoanewerversionofSitefinity,wantedtoprototypeinWordPress.ReallyoutdatedrequiredbyDean'sofficeThenewsitesprovidemorefunctionalitytheoldsystemwasclunky,hardtotrainsomeonehowtouse,notflexibletorespondtochangeandnotresponsiveforphone,etc.ThereweremanyreasonsforustoswitchtoWordpressandCALSsupportedtemplate.Wordpressisquiteeasytouse,oldHTMLbasedsitewasclunkyandhardtoupdate.CALSwasencouraging(and,Ithink,slowlyforcing)CALSbaseddepartmentstoupdatetheirwebsitesanywayanduseWordpressandtheirCSS,soitwastimetomove!ThisisanewwebsiteToocomplicatedtouseforourpurpose

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 6 of 44

  • Toocumbersometouseandnooneseemedtoknowhow.

    upgradetostandardtemplatefromtheuniquetemplatewewereonbefore(seecommentsonpreviousquestion)UWstoppedDrupalsupportWantedtousetemplatessimilartorestoftheUW.Andcleanthingsup.Wasnolongerbeingsupported.Toldweneededtomoveit.Wasn'therewhennewwebsitewasdesigned.WemigratedtoCMSbecausetheversionwewereonwasoldandoutdated.WemovedovertotheCALSplatformbecauseofreducedeffortforsimilarqualityresult,andforincreasedsecurity.Wehaveslightlydecreasedflexibility,buthavebetterconsistencyofformatwithotherDepartmentsinCALS.weneededmorethananoccasionalupdateandmovedtoWIscWebto/changethelooktoconformwithmostuniversitysites/allowforablog/easiertoupdate(lastsitewasanightmare)WeneededrebrandingWeneededtobeabletoeditanddesignwithoutgoingthroughsomeoneexternal.IuseWiscWebfortheportalandGoogleAppsforthecontentpages.WeneededtoupgradebasedonwhatwewouldbesupportedonWewantedtohavecontentownersdotheirownpages.Wewantedtomovetoasystemwhereourwebsiteswereeasiertoupkeep.Wewerehandcodingpagesbefore,withseveraldozenwebauthorsusingdreamweaver.itjustmadesensetomovetoaCMSWewereinformedfromtheUniversitythattheyarechangingourwebsiteandusingWordPress.WeweretoldweweremigratingtoWordPress.Nochoiceinthematter.Wewereunabletocustomizethesitetomakeitmoreattractiveanduserfriendly.WiscWebCMSwasattractivetousbecauseitisfreeandwehavegreatsupport.WhenclientsleaveWiscWebordont'wanttouseWiscWeb,usabilityandeaseofuseofthecontentauthoringplatformisabigone.OurWordPressclientslikeit'ssimplicityandlowbarriertoentry.WithourprevioussitecontenteditorswereresponsibleforknowingHTMLandCSStocreatetheirpages.Wewantedaneasierwayforthemtopushcontent.Italsoallowsustohavemorecontroloverthecodebeingwrittentohelpensureanaccessibleandresponsivesite.WordPresshaswaytoomanymenuoptionsandIgetconfusedastowhichoneIneedtomakechangesoruploadsomethingnew(it'snotobvious).SomeoptionsIdon'tseemtohaveeverneeded.

    Q32_6_TEXTWhatwereyourprioritieswhenselectingthecurrentplatform?CommentsAbilitytomakearesponsivewebsiteBetterresourcesavailableandeasiertoturnaroundanewsiteinWordPressoverSitefinity.CostandavailabilitycostandavailabilityofsupportforsmalldepartmentwithlimitedITexperience/abilitytostaycurrentwithtechnologywithoutretraininglimitedstaffDean'sofficewantedtohavecontroloflayoutDesireforourwebsitetohaveasimilarlookandfeeltootherUWMadisonwebsites.easeofuseEaseofuseFreeoption,formatisinlinewithuniversitybrandingandfewerdecisionstomakeregardinglayout

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 7 of 44

  • HavingalargersupportstructureatCALS,weanticipatebettersecurityandmoreseamlesspatching/maintenancethanwhatwehadtryingtodoeverythingourselves.HostedandsupportedbyLSSatnocost.OthermembersofourstaffhadexperiencewithDrupal.Ididn'tknowtherewereoptions.Iignoredcost,whichIprobablyshouldpaymoreattentionto!/IlovethesupportIwasnotconsultedIwasnotpartofthatdecisionmaking.Itisfreeandthesupportisgreat,evenwhenrequestingtightturnaroundtimes.Thetrainingshavealsobeenappreciatedandeasytounderstand.ItwasfreewithongoinglongafterI'mgonefreesupport.Itwasalreadybeingusedbyseveralgroupsoncampus(asisDrupalandWordpressbutthosewouldhavecostmoneytocreateANDtomaintain).DoITisrighthereoncampusandveryaccessibleandknowledgable.lookingfora"bestpractice"experienceforprovidinguserfocusedcontenti.e.,notjustforinternal,notjustfor"us"forourstakeholders.//brandingveryimportant,whichwasnottruepriortocurrentsite(weloveit,butmostimportant,ourusers/visitorstothesiteseemtoloveit,too!)lookingforsomethingflexiblethatcanbeeasilychangedandadoptnewdesignneeds.MovingfromDreamweavertoacontentbasedmanagementplatformwasapriorityduetoeaseofeditingaccess.Wealsoknewthiswouldsetusupbetterforfuturewebupgrades.Mygroupwantedtomovefromacustomsolutiontoacampusstandard.Wewantedourdepartmentalsitetohavealookandfeelsimilartothatofothercampusdepartments.WealsowantedaCMSthatwassupportedbycampus,somydepartment'sITstaffwouldnotneedtosupporttheCMS.HavingacentralizedCMSservicesavesustimeandmoney.neededtoallowustosimplifycontentcreation,manageuser(editor)access,simplifytechnicalsupport,anduseasystemsupportedbyothersupportgroupsoncampusOurchoicewastohireanoutsidewebdesigneroruseDrupal,assistedbyLSS.Duetocost,weselectedDrupal.Drupalhasotheradvantages,includingeaseofupdatingformultiplestaff.Responsivedesignwasthetoppriority.Reusingasmuchcontentaspossible.Seeabove;didnotmakethechoice,don'tknowwhytheyshifted.Sincemostapplicationdevelopmenthappensinhouse,wemostlylookedforasystemthatwouldbeeasyforcontenteditorstouseandhadbroadsupportoncampus.TheDeptITpeoplechosetheWordpressformatforus.WedontlikeitthatmuchTheeditingexperienceneededtobeuserfriendly,thecosttodevelop(intime)neededtobelow,theplatformneededtobeinastateofconstantsecurityupdatesandpatches,andthereneededtobealotofgoodpluginsupport(activedevelopmentcommunity)theplatformwaschosenformeIhadusedaformer,easierversionofWordpressinthepastbutthiscurrentversionseemsveryadvancedTimetorevisetheoldsitewasmorethanadecadeolduserfriendlyformembercontributorsUsers'preexistingknowledgeofselectedCMS.(Wordpress)

    UWstoppedsupportforDrupal(whichtheyhadfullyendorsedseveralyearsbefore)andofferedsupportforCMSWantedtotakeadvantageoftheUWtechnicalsupport.WealsochoseWiscWebCMSinordertobuildredundancywithinourdepartmentandenablemultiplenontechnicalstafftoeasilybeaddedaseditors.Wasnotinvolvedinthis.WasnotourdecisiontochangetoWordPress.Wasn'therewhennewwebsitewasdesigned.

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 8 of 44

  • Wearestrugglingwiththetechnicalsupportrightnowbecausewedon'tknowwhatwedon'tknowandIthinkwearegoingtohavetohireaPTexperttohelpwiththetechsidealthoughI'dprefertoworkwithDoITandnotcommittoastaffpositionrightnowWejustupgradedwhatwehadintoanewversionofwhatalreadyexisted.WenowuseWordpress.Easeofusewaskeybecausewehavedistributedediting/publishingrightswithstaffthatmightonlydowebworkoccasionally.

    Q16(Optional)Please,elaboratewithanyotherrelevantdetailsastowhythecurrentplatformchosen.Alignwiththecampusstandard.Becauseitwasaknownproduct.BothofournewsitesareonDrupal.Drupalwasselectedbecauseofit'sabilitytomeetmostofourbusinessneedsoutoftheboxwithlesscustomizationthanWordPresswouldhavelikelyrequired.ThetradeoffwasDrupal'sadmin.interfaceisalittlelessuserfriendlythanWordPress',butitisstillsustainable(nontechnicalfolkscanupdateandmaintainthesitewithminimaltraining).Campussupport,low/nocost,abilitytohavevarioususers/rolescostisamajorfactor.weneedtotakeadvantageofcampusresourcesthatareaffordable.Easeofusewasbigaswedonothaveadedicatedwebdev.FromwhatIunderstandtheoldversionofDNNwasnotgoingtoworkanylongeronaserversowehadtobemovedovertothenewversion.ImaintainthewebsiteandhaveusedDreamweaverinthepast.Wantedtohavefullfunctionality.IwantedtokeeptheplatformwithinUW;hopingtointegratewithotherinfotechideas(eventually)IwaspleasantlysurprisedtolearnthatDoItprovidedtechnicalsupportonWiscWebCMSfreeofcharge.Itookadvantageofthatlastyearsothatwecouldmakemajoroverhaulstooursite.overall,Iamquitesatisfiedwithboththewayithasturnedoutandhowuserfriendlyitis.thereissomecounterintuitivepartstoaddingcontent,butI'mabletofiguremosteverythignout.Inswitchingtoresponsivedesign,wedeterminedthatWordPresscouldprovidethelayoutwedesired,withlessregularupdates,andandeasiereditortoworkwithItwasfreeandsupportedbycampusItwasfree,flexible,accessibletonontechnicalusersanddoitwashelpfulasaresourceIt'sauserfriendlyplatform.Joomlawaschosenasitwastheplatformthedesigner/developerwehiredwasmostexperiencedwith.ManyotherswereusingWPandweresatisfiedwithit;itiseasytosetupanduse.Mobilefriendlypersonresponsibleforcontentmanagmentalsousesplatformforgradandundergradcatalogs,wasfamiliarandabletouseeasilyPrimaryreasons:FREE!andeasilyupdatedamongourstaffwithouttheneedtosendallupdatestoonewebmasterwhocanneverseemtobefoundoreasytocommunicatewith.Ilikethefreedomofbeingabletolearnsomethingnewandapplyitrightaway.Sorry,Idon'tknowanythingaboutplatforms,Ijustwritethecopyandgiveittoourwebpeople.specificallylookedforeventhandling,multiplelayersofadministration,veryeasycmsaswehaveover40+usersforoursiteSupportfromWiscWebCMSstafftomigrateoursite(atnocost)wasextremelyattractivewhenchoosinganewplatform.ThecurrentplatformhadthebestsupportforourLDAP

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 9 of 44

  • TherewasnowebsitebeforeIstartedworkinghere.Istartedone.Iaskedsomeoneandtheytoldmehowtostartone.Ireallydidntchoose,didntknowtherewereotheroptions.userfriendlyWechoseadesignerandadeveloperbasedontheircapabilites,cost,andinitalconcepts.Wetheninturn,askedthemtosuggestaplatformthatwouldbetheCMS.Ididn'tcaretoomuchabouttheplatformaslongasitmetbasicrequirementsof1)Easytoupdate2)Easytoteach/delegatetostudentemployeestoupdate3)Easytomakeiterativechangestodesign/functionality.4)comfortablethatwecouldplug"mostdevelopers"intotheprojectshouldwebecomedissatisfiedwiththeinitialvendors.WechoseWiscWebsowecouldeasilyandcheaplycreateawebsiteforourdepartment.Iwaswhatwasavailablenoncmapustouseforfree.WechoseWiscWebtoconformtotheUniversity's"look"andtohaveDoITsupportandtraining.WechoseWordpressbecauseitwouldworkwithourotherITsystemsandwethoughtitwouldbeeasytofindwebdeveloperswithWordpressexperience.WeconsideredDrupal,butthecorewasmoreapplicationdevelopmentfocusedandwasabittrickyfornontechfolkstouse.LookslikeDrupal8willimprovethisalot,butitwasjusttakingtoolongtogetout.WecopiedtheschoolofagricultureandlifesciencesWeneededamoresustainablemodel.Mostupdatedwerebeingdonebystudentstaffbuttheyallhaddifferentlevelsofexperience.Weneededsomethingthatwastrainable.Wewantedeaseofmaintenance.Iamnotatrueprofessional,sosomethingintuitiveandeasytouseWewereextremelyhappyandimpressedwiththesupportandprofessionalismofLearningSupportServicesthroughL&S.

    WhenIstartedtheprojectIincorrectlyassumedthatthedepartmentstaffhadsomeDrupalorHTMLknowledge.Afterfindingoutthesadhistoryofchangingconsultantsevery2yearsforthelastdecade,IdiscoveredthattherereallywasnogoodreasontostickwithDrupal,butthatdiscoverywas8monthstoolate.WiscWebCMSwaspresentedandunderstoodtobetheplatformofchoicefortheenterprise.WordPresshassomuchmoresupportanddocumentationthanSiteFinitythatmakesdeveloping,addingplugins,etc.muchlesspainful.Wordpresswaschosenduetothelargecommunity,quickpatchesandupdates,andeaseofcontentcreation/editing

    Q18_8_TEXTWewouldliketoknowwhatcontentmanagementplatformsortoolsyouhaveusedanywhere,notlimitetoyourcurrentwebsite.Please,checkalltherelevantitemsbelow.Other1and1MyWebsiteAdobeContributeAngularJSBigRoseCargoCollectiveCMSMadeSimple(CMSMS)CMS,reddot,dotNetNukeCMSMS,JoomlaColdFusionContributeContributeContribute,Frontpage

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 10 of 44

  • Contribute,SquarespaceCustombuiltwebappsandPlone.customCMSbuiltbymarketingfirmcustomcodedplatformcreatedfortheorganizationIworkedfor.CustomplatformcreatedbyBigRoseWebdesignCWIS(http://scout.wisc.edu/cwis/)Desire2Learn,DNN,ActiveServerPages,Confluence,MSExchange,UWKnowledgeBasedjangoDjangoCMS,MezzanineDNNDNNDNN7DoesLearn@UWcount?DoIT'sKnowledgebaseprogramDotNetNuk,RedDotDotNetNukeDreamweaverDreamweaverdrupalscholaredithtmlfilesbyhandExpressionEngineExpressionEngineExpressionEngine,CraftCMS,PerchCMS,Jekyll,SquareSpacegoDaddy,networksolutionsGoogleDriveHomegrownCMSHtml/css(handcodedorwebtemplates,notDreamweaver)HTML/CSSwithnonWYSIWYGeditor(BBedit,NoteTab+)IdonotknowIdon'tknow.IsendupdatestoourITpeopleandtheymakeitallhappen.I'mnotsurewhatourpreviouswebsitewasmanagedon,butitwasn'tWiscWebInhousebuiltCMScalledPAT(builtbyeHealthOfficeUWHospitalandClinics)InhousecustomASP.netCMSInternalRubyonRailsapplicationJoomlaJoomlaJoomlaJoomlaJoomlajoomlajoomlaJoomla!Joomla!,Mambo,Zope/Plone,MediaWikiJoomla,MyWebSpaceJoomla,RedDot(maybethat'swhat'snowreferredtoas"WiscWeb"?)Joomla,WeeblyJSframeworks(Angular,Backbone,Ember),Node.jsbloggingplatforms(Ghost),Joomla(why?!)

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 11 of 44

  • LiferayMarquiCMSMediawikiMicrosoftFrontPagemoodleMoodlenetobjectsfusion,inhousedesignedsoftwareNetBeansNotepad;custombuiltCMS;TerminalFouroldMyWebSpace,OpenAtriumOmekaphpphp/mysqlPHP/MySQLphp/mysqlphp/mysqlcodedsitesPHP/SQLSiteandFTPsharingaswellPloneProprietarytoolforpostingnewsstoriesdevelopedbyNickyearsagoRails,CustomPHP,JekyllrapidweaverSilverstripe,Craft,ExpressionEngineSitecoreSiteCoreand.NetApplicationsSitefinitySiteFinitySitefinitySitefinitySitefinitySitefinitytheContentManagementSystemthatisusedbymostunitswithintheSchoolofEducationSquarespaceSquareSpaceTemplatebasedautomatedgeneration(Sphinx)hostedonGithubpagesTumblr,blogspot,bloggerTypePad.Also,proprietarysystemsdevelopedinmypreviouscampusdepartment.variousproprietarysystemsvendordevelopedcustomCMSvim:)WeusetheDOItpageextensivelyforinternalpolicycommunication.web2pyWeeblyweeblyweeblyandplainHTMLcodewikispaces,FrontpageWixWix,SquareSpace,DreamweaverWix.com

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 12 of 44

  • Q18_9_TEXTWewouldliketoknowwhatcontentmanagementplatformsortoolsyouhaveusedanywhere,notlimitetoyourcurrentwebsite.Please,checkalltherelevantitemsbelow.CommentsBeforewemovedtoWiscWeb,departments/programsloggedintoabranchofourserveranddowloadedWordand/orhtmlfiles.Deptpublicsite+intranetsiteuseDrupal6.PlanwastomigratetoDrupal8,butdelaysinreleaseledustostartdevelopinganewdeptsitewithWordPress.DoingokaywithDreamweaverbutIthinkthefilesaregettingmessy.Dontknow.Dreamweaverisdifficultforustouse.example:http://www.uhs.wisc.edu/occhealth/ergonomics/index.shtmlFoundDreamweaverhardtouseHaveusedgooglesitesforotherorganizationalsupportofcampuswidegroups.Iamnotskilledinwebdevelopment,buthavetodoittohaveawebpresence.ItwouldbesomuchbetterifIhadaprofessionalIcouldusecontinually.IamnotsurehowtoanswerthisIamnotthewebprogrammeranddonottypicallyuseaCMS.Iamthestaffpersonwillingtolearnwhateverplatformthecollegedecidestogowith;thereforeIlearnenoughtoputourcontentupandmaintainthesite.IdonotknowIdon'tknowIdon'tknowwhatifthe"CMS"Iuseisoneofthese.Orforthatmatter,whattheKBis.IhavehadforreasonsoranothertousemanyoptionsbutotherthanWordPressorDrupalmostareinflexiableformostneeds.DrupalhasbeenthemostusefulandflexiableforawiderangeofpurposesalbeitWordPressisusefulforasimplecontentsite.Ihavenoidea.Idon'tmanageourstation'swebsite;mycoworkerdoesthat.IknowWrodPressbutIamnotsurewhatelseIuseWordPressformypersonalwebsiteIusuallyeditmyHTMLbyhand.OurofficestaffusesDreamweavertoupdatethesite.I'mnotsureifdoingablogonWordPresscounts,butIaddedit.IalsoincludedGoogleeventhoughI'veneverhadalivepageonit,buthaveplayedaroundwithit.I'mnotsureofallcontentplatformswe'veused.I'vebuiltalotofwebsitesusingmanydifferentCMSsandtools.Butcurrently,weareexclusivelyusingWiscWebCMS.LiferaywasmiserableMainsiteisSitefinity,othersarecustomcodedASP.NetorplainApache.

    MostsitesareinWorpdress/Wealsohavesiteswrittenwithstraight/HTMl/CSS(wedonotusedreamweaver)usingRubyforneededfunctionality.//WehaveoneJoomlasitewearemigratingoffofinaaweekMyDNNwebsitelaunchedinJanuaryof2006.IconvertedtoCMSinMarchof2012.MyroleismoreadministrativeandadvisingNewssystembasicallyworksfinebuthassomelimitationsandglitches.Ourcollege'smainwebsiteisrunonWiscWeb,whileournewswebsiteusesWordPress.Ourwebsiteisancientandembarassingwehavenoresources(stafftimeormoneytohire)toimprovePHP

    Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only

    Appendix 3 - Page 13 of 44

  • RailsappintegrateswiththepublicandintranetDrupalsitesviawebservicesSincethecreationofourdepartment(formerlyadivision)wehaveusedDOITwebhostingandCMS.SMPHcontrolsformat,weworkthroughthemtomaintainandupdatecontent

    Socialmediacouldbecon