U of A Web Strategy and Sitecore

Editor's Notes

• #2: what we’ll talk about today:\n-where we are today\n-where we were\n-how we got here\n-what we’re doing with Sitecore\n
• #3: \n
• #4: our site today\n\nflexible feature space - first time we’ve done this\n\nconvocation 2012 - biggest operational event, part of a large analytics project\n
• #5: \n
• #6: \n
• #7: sites: registered as subdomains of ualberta.ca\n- some will be ‘off the shelf’\n- some will have custom: looks, colours, design elements, functions\n- some are large, some are small\nusers:\n- from our training centre: users that have registered and completed traing\npages:\n- published. does not include versions or unpublished\nmedia items:\n- images, docs, video, audio\n
• #8: - Google Analytics Sept 2011 through April 2012\n- fall/winter semesters\n- our heaviest traffic period\n
• #9: 22 staff\n- 5 devs\n- 3 html designers\n- 1 db\n- 1 designer/map functions\n- 1 content person\n- 3 PMs\n- 1 Writer/Editor\n- 3 managers: Analytics, PMO, Development\n- 1 ED\n- Admin Assistant\n- 2 Analysts\n- and 1 senior designer\n- 1 contract writer\n- 1 sys admin\n- 3 student interns working on map interiors\n\n
• #10: - where we were\n
• #11: our site in 2008\n\nthis is what got me started in the field of analytics\n
• #12: - our own CMS\n- built by me\n- ColdFusion - tech risk (try hiring CF people)\n- Note ColdFusion was not a choice made by us\n- purchased an app from an external vendor to manage news\n- they built in CF for us\n- before my time (i was ASP dev then)\n- in order to maintain, we went with it\n- not flexible\n- code - out of hand with every little custom request\n
• #13: - hardware needed replacing\n
• #14: - started the process of evaluating what to do\n- no build, we need something where someone else looks after the software\n- open source - sure it’s free to download and install\n- staff time\n- support\n- what if there’s a problem with the code base\n- we have escalated a number of issues to Sitecore\n\n
• #15: - started the process of evaluating what to do\n- no build, we need something where someone else looks after the software\n- open source - sure it’s free to download and install\n- staff time\n- support\n- what if there’s a problem with the code base\n- we have escalated a number of issues to Sitecore\n\n
• #16: - started the process of evaluating what to do\n- no build, we need something where someone else looks after the software\n- open source - sure it’s free to download and install\n- staff time\n- support\n- what if there’s a problem with the code base\n- we have escalated a number of issues to Sitecore\n\n
• #17: - started the process of evaluating what to do\n- no build, we need something where someone else looks after the software\n- open source - sure it’s free to download and install\n- staff time\n- support\n- what if there’s a problem with the code base\n- we have escalated a number of issues to Sitecore\n\n
• #18: - keep the committee small, bare minimum\n- progressive members\n- show everyone the process\n- because it’s a big purchase, need the RFP\n
• #19: - this is what we need\n\n
• #20: - this is what we need\n\n
• #21: - this is what we need\n\n
• #22: - this is what we need\n\n
• #23: - this is what we need\n\n
• #24: - this is what we need\n\n
• #25: - this is what we need\n\n
• #26: Very detailed RFP\n\nrisk of getting a few or just a single qualified vendor\n\nwhat it did - limited the submissions we had to go through\n\n3 qualified - easy shortlist\n
• #27: \n
• #28: CMS Watch: $1000 for reports on your finalists\nDog and pony show. Here’s our site. Build it in your product and show us.\nSet it up for us and we’ll see what we can do.\nWe went right in to the code (I broke Sitecore in my first 20 minutes)\n
• #29: \n
• #30: RFP closed in march, 2008\nreview in April\ndemos and trials in april/may/june\npilot builds begin with external vendor\n\nkeep in mind - doing all this with 5/6 staff\n
• #31: - the first real project where we are moving things to the next level\n
• #32: - the first real project where we are moving things to the next level\n
• #33: - the first real project where we are moving things to the next level\n
• #34: Reorg:\n- New ED\n- New direction\n- new funding model\n-\nProjects:\n- rebuild our web presence\n- rebuild our team’s role at the University\n- rebuild our Sitecore instance\n
• #35: - rebuild sitecore\n- HTML5\n- go back, evaluate or code. fix and improve. use lessons we’ve learned\n- document and build it so outside devs that are sitecore certified can step in and work on projects\n\n- redesign site\n- go back and undo everything that was done previously\n- use the data we have - by this time we have a fairly good data set from GA and some customizations\n- get new data by using our own resources in our faculties to focus group, survey, interview, etc\n
• #36: - put the word out that we’re redesigning - want the community’s help\n- 2000+ people fill out online survey from extension\n- 200+ of those say send me more\n- using tools at Usability Hub, email and get them to perform tests\n- Tribal DDB in Vancouver works with our office and the RO on 2 projects. Do their own research and help with the IA, wireframing and sitemaps then move to design comps\n- we take designs, code ourselves in Sitecore (make a few changes)\n
• #37: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #38: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #39: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #40: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #41: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #42: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #43: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #44: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #45: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #46: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #47: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #48: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #49: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #50: - LAUNCH Sept 1, 2011\n- during the summer we lost 2 staff members, went through the process of hiring all our new staff (hired ~6)\n- some of the staff brought on in July and August were thrown right into the fire to get this done\n- FLEXIBILITY - each landing page has different needs and serves a different funnel. Flexible design allows us to change layout, text and calls to action.\n- All HTML5\n
• #51: \n
• #52: \n
• #53: \n
• #54: \n
• #55: \n
• #56: \n
• #57: \n
• #58: \n
• #59: \n
• #60: \n
• #61: - Content sharing in place\n- create in one location\n- issue to solve: doesn’t always display in the same place or same format\n- modify with CSS depending on the location\n
• #62: - sharing of news articles\n- PR creates article\n- if it’s about your faculty, pull it into your site via sitecore\n- \n
• #63: - shared content has it’s own folder in our Sitecore Meta Data.\n- unformatted. content only\n
• #64: - shared content has it’s own folder in our Sitecore Meta Data.\n- unformatted. content only\n
• #65: - shared content has it’s own folder in our Sitecore Meta Data.\n- unformatted. content only\n
• #66: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #67: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #68: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #69: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #70: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #71: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #72: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #73: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #74: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #75: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #76: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #77: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #78: - Campus maps\n- one of the big needs we had was to improve our map\n- go from a static image map with 4 quadrants with zoom to a quadrant only with numbers and a legend\n- to an interactive map using Google maps and additional features\n- layered map\n- services\n- social media\n- building details\n- built the custom interface using the Maps API\n- data stored in sitecore and published as a KML file that gets layered on top of the base Map\n
• #79: - events calendar\n- UofA is a google Apps client: Mail, Calendaring and documents\n- Google Calendar is now the tool for evnets\n- users have their own calendars\n- input events\n- main feed pulls all events in and shows by date, faculty or subject\n
• #80: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #81: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #82: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #83: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #84: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #85: - Different needs for sports\n- custom data\n- rebuilt from another ColdFusion app (yes, build by yours truly)\n- separate DB on the Sitecore Serve\n- separate interface accessed through sitecore\n- Publish on demand\n- Real time scores\n
• #86: - asset management\n- Marketing and Communications manages assets, upload versions to Sitecore\n- users select which versions they want, make request, ccid is verified and zip file available for download\n
• #87: - Config settings\n- Site Admins can modify a number of elements on their site\n- design elements:\n- colours\n- css styles\n- background images\n- nav elements\n- main nav\n- footer\n- hide/show elements\n
• #88: Tools:\n- this is where we get to the stuff I care about now.\n- all sites have the option to add scripts that are either\n- site wide\n- limited to single page\n
• #89: Tools:\n- this is where we get to the stuff I care about now.\n- all sites have the option to add scripts that are either\n- site wide\n- limited to single page\n
• #90: \n
• #91: \n
• #92: \n
• #93: \n
• #94: \n
• #95: \n
• #96: \n
• #97: \n
• #98: \n
• #99: \n
• #100: \n
• #101: \n
• #102: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #103: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #104: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #105: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #106: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #107: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #108: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #109: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #110: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #111: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #112: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #113: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #114: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #115: - the big benefit\n- placing a universal GA account automatically on all our sitecore sites\n- every page is automatically tagged\n- ensures analytics are always on\n- backup for data\n- BIGGEST piece for proper attribution\n- with many sites, each site would have its own GA code and set of reports\n- who can see\n- who has access\n- what if they leave (and they have)\n- Rollup account and set up procedure\n
• #116: \n
• #117: \n
• #118: - example\n- interactive submission based on your preferred tool\n- tools such as storify easy to add using the edit HTML feature\n
• #119: - page level\n- jQuery is included on all sites\n- use it to do whatever you need.\n
• #120: \n
• #121: \n
• #122: \n
• #123: \n
• #124: \n
• #125: \n
• #126: \n
• #127: \n
• #128: \n
• #129: \n
• #130: \n
• #131: \n