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.

HighEdWeb 2017 - Unbundle Your Institution: Building a Web Ecosystem

931 views

Published on

Stop me if you have heard queries like these before:

Why am I using {Product X} to build a {Task Y} website?
Why am I rebuilding {Product X} to act like {Product Y}?
Why can’t this {organizational asset} be flexible for {Product Y} instead of just {Product X}?

Questions like these highlight an issue we face more in our day-to-day work in the ever-evolving web: content management system tunnel vision. Sometimes, our organization gets fixated on a particular platform or content management system, even when alternatives and successors exist. And over time, this stagnation hinders growth, expansion, trends, technologies, and eventually even adoption.

In this presentation, I will cover the value of creating a web system ecosystem in your institution, department, unit, or organization. I'll cover:

On-Campus CMS Usage Today - Discussion on scenarios where a CMS is being reconfigured to meet a demand it wasn’t meant to do, and the fallout from said reconfiguration. Why this approach is expensive in the long haul.
What is a Web CMS Ecosytem? - Discussion on a different look at a system, where CMSs are provisioned and recommended for uses and have affordances and tradeoffs.
Change the Community Mindset - Let’s consider the growth, explosion, and fall of CMS systems and stay on top of trends, platforms, and best-practices.
Exploring Ecosystem Adoption- Discussion on changing mindsets, running pilot studies, experimentation, exploration, and research to determine organizational web makeup, goals, needs, and expectations.
Angle Your Institutional Assets - Discussion on side-effects of this move, which may include CMS-agnostic branding and style guides, flexible and scalable plugins and campus application integrations for each system, and pain-minimized migration paths between services and applications.

Published in: Internet
  • Be the first to comment

HighEdWeb 2017 - Unbundle Your Institution: Building a Web Ecosystem

  1. 1. UNBUNDLE YOUR INSTITUTION CREATING A WEB ECOSYSTEM
  2. 2. INTRODUCING MYSELF
  3. 3. THAT’S ME!
  4. 4. SEMBRAT ERIC
  5. 5. ATL & GEORGIA TECH
  6. 6. @ESEMBRAT
  7. 7. WEBBEH.COM
  8. 8. LET’S TALK WEB ON CAMPUSES
  9. 9. OUR USERS USE THE WEB IN UNIQUE WAYS
  10. 10. STUDENTS UNDERGRADUATE GRADUATE FACULTY / STAFF
  11. 11. STUDENTS STUDENT ORGANIZATIONS PROJECT / ASSIGNMENTS COURSES / LMSPERSONAL / PORTFOLIO RESEARCH INITIATIVES & MORE
  12. 12. FACULTY / STAFF UNITS / DEPARTMENTS EVENTS ORGANIZATIONS / GROUPSPROJECTS NEWS WORKFLOW & MORE
  13. 13. WE NEED HELP BUILDING THESE PLATFORMS & SITES. HOMEGROWN / CUSTOM 
 USUALLY CAN’T CUT IT.
  14. 14. WE TURN TO: SYSTEMS, FRAMEWORKS, & PLATFORMS TO EASE BURDEN.
  15. 15. WE COMMONLY GET STUCK
 INNOVATING AND SETTLE 
 WITH ONE SYSTEM.
  16. 16. CHANGE IS HARD. VARIETY IS EXPENSIVE. BUT IS GOING SOLO BAD?
  17. 17. YESIGNORING OTHER/BETTER TOOLS FOR A WEBSITE 
 MAKES YOUR JOBS MORE COMPLEX AND FRAGILE
  18. 18. LET’S CONSIDER…
  19. 19. ENTER THE SCENARIO… YOU’RE A DRUPAL CAMPUS. AND YOU WANT TO OFFER A WEBSITE SERVICE SOLUTION.
  20. 20. WORDPRESS BLOG MULTI- USER INSTALLATION DRUPAL MULTISITE BLOG INSTALLATION 5 HOURS SETUP 30 HOURS SETUP 1 HOUR MAINTENANCE 10 HOURS MAINTENANCE 1 HOUR NEW FEATURES ? HOURS NEW FEATURES
  21. 21. WORDPRESS BLOG MULTI- USER INSTALLATION DRUPAL MULTISITE BLOG INSTALLATION 5 HOURS SETUP 30 HOURS SETUP 1 HOUR MAINTENANCE 10 HOURS MAINTENANCE 1 HOUR NEW FEATURES ? HOURS NEW FEATURES WHICH WOULD YOU CHOOSE?
  22. 22. VS
  23. 23. AND
  24. 24. AND WEB ECOSYSTEM 101.
  25. 25. DRUPALWORDPRESS CMS LAND STATIC GENERATORS PLATFORMS KALTURA SHAREPOINT WIKIS FORUMS ORGSYNC DIGITAL ASSET MGMT. LMS ETC. INTO INFINITY ONE OFF PROJECTS
  26. 26. DRUPALWORDPRESS CMS LAND STATIC GENERATORS PLATFORMS KALTURA SHAREPOINT WIKIS FORUMS ORGSYNC DIGITAL ASSET MGMT. LMS ETC. INTO INFINITY ONE OFF PROJECTS
  27. 27. WITHOUT A GUIDING HAND, CAMPUS WEB IS GOING TO
 SEGMENT AND SILO UP. AND THOSE WEB SITES WILL REBUILD RESOURCES.
  28. 28. FOLKS WILL REINVENT THE WHEEL. OVER. AND OVER. 
 AND OVER. AGAIN.
  29. 29. A WEB ECOSYSTEM, THEN, IS…
  30. 30. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE STATIC WEBSITE ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES
  31. 31. A WEB ECOSYSTEM IS A COLLECTION OF PLATFORMS, TOOLS, 
 SERVICES, AND ASSETS TO BLEND CAMPUS WEB IDENTITY ACROSS ANY* APPLICATION.
  32. 32. PLATFORM
  33. 33. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE STATIC WEBSITE ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES
  34. 34. STATIC WEBSITE ASSETS CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM CONTENT REPOSITORIES BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW PORTFOLIO TOOL SUPPORT INFRASTRUCTURE
  35. 35. WHERE, PHYSICALLY, DOES YOUR WEB OFFERINGS LIVE?
  36. 36. THE CLOUD
  37. 37. ON SITE
  38. 38. WHEN CONSIDERING WHERE YOUR PLATFORMS SHOULD LIVE: FEATURES SECURITY UPDATES SUPPORT
  39. 39. TOOLS
  40. 40. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE STATIC WEBSITE ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES
  41. 41. STATIC WEBSITE ASSETS CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM CONTENT REPOSITORIES BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW PORTFOLIO TOOL SUPPORT INFRASTRUCTURE
  42. 42. TOOLS ANSWER THE QUESTION. WHAT HELPS ME DO THE 
 JOB OF WEB DEVELOPMENT?
  43. 43. TOOLS PROVIDE WORKFLOW FOR CODE AND DEPLOYMENT. HOW DO I BACK UP? PULL DOWN/PUSH UP CODE? WHAT SCAFFOLDS EXIST?
  44. 44. 2 PRIMARY FORMATS.
  45. 45. CODE HELPERS. PREPROCESSORS, VARIABLES, AND REUSABLE CODE CHUNKS.
  46. 46. A LIVING BREATHING DOCUMENT. TAKES THE DON’T-REPEAT- YOURSELF APPROACH TO 
 CODE SNIPPETS.
  47. 47. CODE SHARING, ARCHIVAL, AND VERSIONING. ALLOWS FOR COLLABORATION ACROSS CAMPUS (& BEYOND!)
  48. 48. SERVICES
  49. 49. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE STATIC WEBSITE ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES
  50. 50. STATIC WEBSITE ASSETS CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM SUPPORT INFRASTRUCTURE / 
 SHARED ASSETS CONTENT REPOSITORIES BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW PORTFOLIO TOOL
  51. 51. DRIVEN BY A TOOL KIT OF PLATFORMS AND SYSTEMS SUPPORTED AND LEVERAGED. CAMPUS WEB DOSSIER.
  52. 52. 4LEVELS OF COMPLEXITY FOR CAMPUS WEBSITES.
  53. 53. STATIC/OLD WEBSITES THAT NEED A FRESH COAT OF PAINT BROCHUREWARE/LOW-LEVEL WEBSITES THAT BENEFIT FROM SHARED ASSETS COMPONENT/OBJECT-BASED WEBSITES LEVERAGING A CMS TO STORE/DISPLAY DATA CUSTOM-FIT APPLICATIONS A LA CRM, DAM, REPOSITORIES, ETC.
  54. 54. SHARE RESOURCES AND ASSETS (THEME) BETWEEN ALL FOUR ASPECTS AS MUCH AS POSSIBLE. REUSABILITY IS KEY.
  55. 55. STATIC/OLD WEBSITES THAT NEED A FRESH COAT OF PAINT BROCHUREWARE/LOW-LEVEL WEBSITES THAT BENEFIT FROM SHARED ASSETS COMPONENT/OBJECT-BASED WEBSITES LEVERAGING A CMS TO STORE/ DISPLAY DATA CUSTOM-FIT APPLICATIONS A LA CRM, DAM, REPOSITORIES, ETC. STATIC SITE GENERATOR VERY LIGHT CMS LIGHT CMS BLOGGING PLATFORM HEAVY CMS CUTTING EDGE WEB FRAMEWORK DIGITAL ASSET REPOSITORY CUSTOMER-RELATIONSHIP MANAGEMENT
  56. 56. BROCHUREWARE/LOW-LEVEL WEBSITES THAT BENEFIT FROM SHARED ASSETS COMPONENT/OBJECT-BASED WEBSITES LEVERAGING A CMS TO STORE/ DISPLAY DATA CUSTOM-FIT APPLICATIONS A LA CRM, DAM, REPOSITORIES, ETC. LIGHT CMS BLOGGING PLATFORM HEAVY CMS CUTTING EDGE WEB FRAMEWORK DIGITAL ASSET REPOSITORY CUSTOMER-RELATIONSHIP MANAGEMENT STATIC/OLD WEBSITES THAT NEED A FRESH COAT OF PAINT STATIC SITE GENERATOR VERY LIGHT CMS SHARE CONFIGURATION AND ASSETS WITHIN EACH TYPE.
  57. 57. STATIC/OLD WEBSITES THAT NEED A FRESH COAT OF PAINT BROCHUREWARE/LOW-LEVEL WEBSITES THAT BENEFIT FROM SHARED ASSETS COMPONENT/OBJECT-BASED WEBSITES LEVERAGING A CMS TO STORE/ DISPLAY DATA CUSTOM-FIT APPLICATIONS A LA CRM, DAM, REPOSITORIES, ETC. STATIC SITE GENERATOR VERY LIGHT CMS LIGHT CMS BLOGGING PLATFORM HEAVY CMS CUTTING EDGE WEB FRAMEWORK DIGITAL ASSET REPOSITORY CUSTOMER-RELATIONSHIP MANAGEMENT AND WHENEVER POSSIBLE, SHARE THROUGHOUT THE SPECTRUM.
  58. 58. ASSETS
  59. 59. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE STATIC WEBSITE ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES
  60. 60. CAMPUS END-USERS CAMPUS WEB SUPPORT TEAM BLOG / MICROSITE HEAVY CMS / WEB PLATFORM CRM / FORM / WORKFLOW SUPPORT INFRASTRUCTURE / 
 SHARED ASSETS PORTFOLIO TOOL CONTENT REPOSITORIES STATIC WEBSITE ASSETS
  61. 61. REUSABLE COMPONENTS. PLUG-AND-PLAY ELEMENTS.
  62. 62. STATIC WEBSITE ASSETS THEME / BRANDING NEWS / EVENTS TOOL DIRECTORY TOOLEMERGENCY INTEGRATION ACCESSIBILITY TOOLS LOGO REPOSITORIES
  63. 63. ABOVE ALL ELSE. DOCUMENTATION.
  64. 64. STATIC WEBSITE ASSETS THEME / BRANDING NEWS / EVENTS TOOL DIRECTORY TOOLEMERGENCY INTEGRATION ACCESSIBILITY TOOLS LOGO REPOSITORIES DOCUMENTATION
 
 HOW/WHY/WHERE/WHEN.
  65. 65. THE UNSPOKEN ELEMENT
  66. 66. COMMUNITY
  67. 67. OUR SUBJECT-MATTER-EXPERTS. CONSUMERS, CONTRIBUTORS, AND KNOWLEDGE-MAKERS.
  68. 68. BUILD A COMMUNITY-OF-PRACTICE. BUILD COMPETENCY, EXPERTISE, AND EXPERIENCE FOR USERS OUTSIDE OF YOUR TEAM.
  69. 69. STATIC WEBSITE ASSETS PLATFORMS, TOOLS, SYSTEMS WEB SUPPORT STAFF END USERS
  70. 70. REUSABLE COMPONENTS AND THEME FRAMEWORKS. USE-CASE DRIVEN WEB SOFTWARE AND BEST PRACTICES. WEB EXPERTISE AND RESEARCHERS. A COMMUNITY OF PRACTICE FOR BUILDING, MAINTAINING, AND ENCOURAGING GROWTH AND EXPERTISE.
  71. 71. MAKING THE CHANGE
  72. 72. ONE MAJOR CAVEAT. DISTRIBUTED WEB CAMPUSES WILL TAKE LONGER TO SEE RESULTS.
  73. 73. 1.DEFINE YOUR END-GOAL GOAL.
  74. 74. LOOK AT YOUR PRESENT WEB INFRASTRUCTURE. WHAT WORKS? 
 WHAT DOESN’T?
  75. 75. MOST IMPORTANTLY… WHAT IS MISSING?
  76. 76. CONSIDER YOUR END-USERS. YOUR STAKEHOLDERS. AND YOUR EXPERTS. HOW CAN THEY BE A FORCE FOR CHANGE?
  77. 77. ADVERTISE YOUR END-GOAL. SHOWCASE THE BENEFIT AND CURRENT LIMITATIONS.
  78. 78. 2.GET CAMPUS BUY-IN/INPUT.
  79. 79. REACH OUT TO WEB USERS AND WEB DEVELOPERS ON CAMPUS. ASK THEM THE SAME THREE QUESTIONS YOU ASKED YOURSELF.
  80. 80. WHAT WORKS? WHAT DOESN’T WORK?
 WHAT’S MISSING? YOU’LL FIND SOMETHING YOU DIDN’T EXPECT.
  81. 81. IF DECENTRALIZED… FIND PARTNERS, SUPPORT, OR BUY-IN FROM CENTRAL UNITS.
  82. 82. IF DECENTRALIZED… FIND PARTNERS, SUPPORT, OR BUY-IN FROM CENTRAL UNITS. PLAY THE POLITICS GAME.
  83. 83. 3.FIND A POTENTIAL FIX, AND MAKE THE CHANGE.
  84. 84. PROOF OF CONCEPT.
  85. 85. IF DECENTRALIZED, 
 THIS SHOULD BE EASY. IF CENTRALIZED, 
 TAKE A LOOK AT WHAT RESOURCES YOU’RE WORKING WITH TODAY.
  86. 86. FIND AN ‘EASY WIN' PROJECT. GO THROUGH THE PROJECT PHASES TO TEST A SOLUTION 
 (AT A SMALLER SCALE).
  87. 87. WHERE TO FIND ISSUES? ASK WEBDEVS. ASK WEB USERS. ASK CENTRAL WEB GROUP*. ASK YOURSELF WHAT’S MISSING.
  88. 88. 4.PUSH FOR CHANGE. OR MAKE CHANGE.
  89. 89. BEGIN BEING THE CHANGE 
 YOU WANT TO SEE. GET BUY-IN FROM LEADERSHIP, 
 DEVELOPERS, AND END-USERS. 
 BRING CHANGE TO YOUR CAMPUS!
  90. 90. BEGIN BEING THE CHANGE 
 YOU WANT TO SEE. GET BUY-IN FROM LEADERSHIP, 
 DEVELOPERS, AND END-USERS. 
 BRING CHANGE TO YOUR CAMPUS! PLAY THE POLITICS GAME.
  91. 91. BEGIN BEING THE CHANGE 
 YOU WANT TO SEE. GET BUY-IN FROM LEADERSHIP, 
 DEVELOPERS, AND END-USERS. 
 BRING CHANGE TO YOUR CAMPUS! COMMUNITY BUILD!
  92. 92. FORWARD PLANNING
  93. 93. YOU CAN’T PREDICT THE FUTURE. YOU CAN PLAN FOR CHANGE. AND FOR GROWTH.
  94. 94. CONSIDER THE MIGRATION: DRUPAL 7 (PHPTEMPLATE) DRUPAL 8 (SYMFONY, TWIG)
  95. 95. PLANNING AN ECOSYSTEM 
 ISN’T JUST ABOUT TODAY. IT’S ABOUT LOOKING FORWARD
  96. 96. WHERE TO LOOK?
  97. 97. OUTSIDE HIGHER-ED.
  98. 98. COMMUNITIES OF PRACTICE.
  99. 99. IN THE WILD…
  100. 100. A QUICK NOTE. AS MY CAMPUS IS HEAVILY DECENTRALIZED, I DON’T SPEAK FOR THE CAMPUS AS A WHOLE.
  101. 101. HOWEVER, I DO SPEAK FOR THE WEB DEVELOPERS. MY WORK PRIMARILY IS WITH COMMUNITY-BUILDING AND SUBJECT-MATTER-EXPERTISE.
  102. 102. AROUND 2011.
  103. 103. DRUPAL WAS KING. ALL WEBSITES USED DRUPAL BECAUSE THERE WAS NO ALTERNATIVE FOR ‘SUPPORT’.
  104. 104. DRUPAL THEME 200 WEBSITES WITH CENTRAL CAMPUS THEME. ~300 WEBSITES WITHOUT A CENTRAL CAMPUS THEME. THE WILD WEST FOR ALL OTHER WEBSITES.
  105. 105. THE PROBLEM… ONE SYSTEM CAN’T DO IT ALL. AND ATTEMPTS TO DO SO AGED POORLY.
  106. 106. IN 2017
  107. 107. DRUPAL STILL REIGNS. BUT DRUPAL ISN’T A FIT FOR EVERYONE. BECAUSE DRUPAL ISN’T EASY.
  108. 108. WORDPRESS RULES FOR THE 
 DIY WEB USER ON CAMPUS. SO WE TOOK WORDPRESS AND TURNED IT INTO A SERVICE.
  109. 109. HTML WEBSITES CONTINUE TO SURVIVE AND DECAY. SO WE’RE LOOKING INTO WAYS TO MAINTAIN, ARCHIVE, OR SUPPORT THOSE WITH LITTLE OVERHEAD.
  110. 110. AGNOSTIC THEME FRAMEWORK 800 DRUPAL WEBSITES WITH CENTRAL CAMPUS THEME. WORKFLOW TO ENCOURAGE NEW WEBSITES TO ECOSYSTEM COMPONENTS. 800 WORDPRESS WEBSITES WITH CENTRAL CAMPUS THEME. COMMUNITY-OF-PRACTICE AND EXPERTS ACROSS CAMPUS TO BUILD AND EXTEND. STATIC SITE GENERATOR PROOF OF CONCEPT WEBSITE-AS-A-SERVICE A WORK IN PROGRESS.
  111. 111. HOW DID WE DO THIS?
  112. 112. COMMUNITY BUILDING WAS KEY. PASSING ON KNOWLEDGE TO 
 OUR END USERS ALLOWED DECENTRALIZATION TO REALLY MEAN DEMOCRATIZATION.
  113. 113. WORDPRESS WAS THE RESULT OF TWO COLLEGES TEAMING UP. FIXING THE CHALLENGE OF ‘MICROBLOGS’ AND ‘BROCHUREWARE’ WEBSITES.
  114. 114. DRUPAL 8 IS COMING… AS AN END RESULT OF OUR COLLEGES AND 
 EXPERIMENTATION.
  115. 115. OLD WEBSITES ARE BEING PHASED OUT. SECURITY CONCERNS SINGLE-SIGN-ON NEWS/EVENTS INTEGRATION
  116. 116. BUT IT’S WORTH NOTING…
  117. 117. THERE’S STILL WORK TO DO.
  118. 118. QUESTIONS?

×