Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

October 2016 - edUi - Save Us, Self Service!

230 views

Published on

This session will cover Georgia Tech’s exploration, selection, development, and processes behind Professional Web Presence, a self-hosted and self-maintained WordPress Multisite hosting over 350 faculty and staff websites maintained by over 700 campus accounts (as of March 2016).

This session will detail:

The exploration process – What issue are we solving? Why solve this issue? What do websites across campuses look like?
The evaluation and selection – What systems exist to serve this need? Pros and cons of each? What led to our selection? How do you decide?
Develop, and develop some more – What is needed for a rollout? A phase one? Phase two? Long-term growth and feature-sets? What tools exist to aid this scaffolding? What can the community provide?
Processes and onboarding – How do you bring in community? Build in comfort?
Low-level PHP or web development knowledge is not mandatory for this session.

What you’ll learn:
What opportunities Self-Service web gives your smaller, independent, research units on campus
How to initialize a project to kickstart self-service tools
What directions to go in to help scaffold development of your self-service assets (themes, modules), if you're not a subject matter expert in all things code
What we've seen from self-service, adoption, and hesitation
Opportunities in self-service for brand compliance, brand flexibility, and customization

Published in: Education
  • Be the first to comment

  • Be the first to like this

October 2016 - edUi - Save Us, Self Service!

  1. 1. Hosting and Administering Multiuser CMSs for Higher Education Eric Scott Sembrat October 2016 edUi Conference SaveUs,SelfService!
  2. 2. Eric Sembrat Web Manager at Georgia Tech Graduate Student at Georgia State Lives in Atlanta, GA Ziggy.DOGHubble.DOGSara.FIANCEE @esembrat webbeh.com
  3. 3. edui@edui: ~$ ./agenda-for-today 1 Common Problems with Web The issues we all face on a daily basis - documentation, best practices, and security. 2 Self-Service Web 101 Get the details on what self-service is, who is leveraging it, and the benefits. 3 How do I Self-Service? A quick synopsis of the project plan for selecting a self-service application. 4 Growing Your Application Now that you have an application, how do you maintain and extend it for your unit?
  4. 4. Oh,OurCommon WebProblems
  5. 5. Whenlookingatlarger decentralizedorganizations, there’sacommonthreadin issuesandproblems facingwebdevelopment. thewebisn’talright
  6. 6. Branding
 Experience
 Security
 Technology 4areasofconcern:
  7. 7. Branding
  8. 8. branding education ismoreimportant
 thanever.
  9. 9. branding however,mostDIY attempts are dreadful
  10. 10. examples let’sseesome
  11. 11. Typicallyrequiretechnical expertisetoaccurately implement. brandingresources Tendtolagbehind centrally-maintained trendsandbestpractices.
  12. 12. Experience
  13. 13. webeditors smallscaleunitshave whicharen’tregularwebusers
 orwhichhavemanymorejobduties.
  14. 14. teachable? CSS,Javascript,PHP,CMSAPIs… or,isthereabetterway?
  15. 15. Security
  16. 16. security today,we’reforcedtoconfront fromallareasofweb.
  17. 17. ServerLayer
 WebApplicationLayer
 WebApplicationPlugins
 UserAccounts DDoS
 Phishing
  18. 18. experts doweforceourwebuserstobe inupdatingandsecuritymanagement?
  19. 19. access or,moreimportantly tosecurityandupdates? shouldweevengiveend-users whynot centralize?
  20. 20. Technology
  21. 21. websites howdowekeep uptospeedonbest-practices?
 strictforlegalrequirements? readyforupcomingtrends?
  22. 22. responsive takethelastbigseismicshift:
  23. 23. mediaqueries? doyoursmallwebsiteownerswrite
  24. 24. https whatabout ?
  25. 25. Self-service totherescue
  26. 26. once wouldn’titbegreatifthese challengescouldbefixed forallwebsitesunderan
 umbrella?
  27. 27. self-service enter
  28. 28. self-service whatis anyways?
  29. 29. self-serviceseparatesthe setup&configuration fromthe sitemaintenance
  30. 30. Sets up configuration. applicationmaintainers: end-users: Selects and configures appearance. Creates and edits content. Enables features and plugins. Applies security + app updates. Adds new features and plugins. Develops campus-specific features. Conducts training.
  31. 31. provisioned websitesare notconstructed.
  32. 32. user-created contentis usingcurated/approvedassets.
  33. 33. whousesthis?
  34. 34. (andmore)
  35. 35. SelectaCMSfor development
  36. 36. planning thekeychallengeis and logistics
  37. 37. planning whoisthisintendedfor?
 whatismyend-goal? whatismysuccessmetric?
 wherewillthissystemlive? whatsystemsareavailable?
 whatframework/systemwillIuse?
  38. 38. logistics whatfeaturesareneeded? whatpluginsarerequired? willIneedatheme? willIneedcustomplugins? whatabouttraining? whataboutdocumentation?
  39. 39. cost and,aboveall (whatcanweafford?)
  40. 40. productprice costiseitherdeterminedby: development price or(usually)
  41. 41. eachhavetheirprosandcons. productcost
  42. 42. eachhavetheirprosandcons. development cost
  43. 43. howtofind afteransweringallthequestions possiblesolutions?
  44. 44. 1 talktopeerinstitutions researchtheirsolutions,
 challenges,projects,and
 futureoutlook.
  45. 45. 2 initiateabetatestgroup findtestusersinyour
 primaryaudiencestoserve
 aspristineguineapigs. theirfeedbackisgenuine.
  46. 46. 3 findpotentialsolutions afterresearch,cometothe
 tablewithoptionsfora
 solution. (cost,features,flexibility,etc)
  47. 47. 4 test,react,andanalyze letyourbetatestersexplore. letthembreakthings.seeif
 whatyourgoalsarematch
 reality. makenotes.interview.keep
 metrics.
  48. 48. 5 touchbasewithreality lookatresultsand
 summarizeallmajorkey
 points,challenges,and
 successesforeachtool.
  49. 49. 6 takeabreak. you’vedonealotsofar.
  50. 50. 7 weigheachoption. scoresolutionbyits
 strengthsandweakness. comparewithcurrenton- campussolutions.
  51. 51. 8 fin. younowhavealist ofsolutionsthatfit yourrequirements.
  52. 52. customization armedwithdata,nowit’sallabout
  53. 53. Customization andgrowth
  54. 54. campus integration thetime-consumingcreature
  55. 55. development usuallyinvolves work
  56. 56. thingstoconsider: whatcustomservicesexist? whatarethebrandingrequirements? whatunitswillneedtoworkwith? newcampusinitiatives?
  57. 57. whatcustomservicesexist? considerfacultydatabases,news/ eventservices,userauthentication, etc.
  58. 58. integrating thevalueof shouldoutweighresources
  59. 59. standardize theseserviceswould practicesandworkflow.
  60. 60. buy-in andcreatethealmighty forprospectiveusers.
  61. 61. whatarethebrandingrequirements? legalrequirementsforaccessibility. brandingcampaigns,logousage,and header/footerrequirements.
  62. 62. edge-cases keepinmind fortheodd-balls.
  63. 63. whatunitswillneedtoworkwith? thinkaboutorganizationsthathave complementaryservices,suchasthe domainregistrar.
  64. 64. partners thinkof andaffectedunitsoncampus.
  65. 65. newcampusinitiatives? lookaheadtoupcomingtrends, policies,campaigns,initiativesand planaccordingly.
  66. 66. Casestudy:
 GeorgiaTech
  67. 67. pwp.gatech.edu
  68. 68. goals: OutletforLab/Center/PersonalWebsites StandardizeandExtendBranding
 MitigatelegacyCMSsecurityvulnerabilities Meetneedofabloggingplatform ProvideeasierCMSthanon-campusDrupal
  69. 69. whodidwelookat? GeorgiaStateUniversity
 OpenScholar DrupalMultisite
  70. 70. howdidwechoose? Ourtestusersandtheirresponses.
  71. 71. whatdidwedevelop? GTtheme(GTBoilerplate). GTbrandingplugin. GTCASplugin. GTSiteMaintenanceplugin. GTnews/eventsplugin(WIP). GTdirectoryplugin(WIP).
  72. 72. currentchallenges Maintainedby0.2FTEtimeover3staff. Enhancedsecuritymeasures. Back-portingDrupaltoWordPress.
  73. 73. questions?
  74. 74. Eric Sembrat Web Manager at Georgia Tech eric.sembrat@coe.gatech.edu @esembrat webbeh.com

×