Your SlideShare is downloading. ×
Synchronizing Creativity with Content Management
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Synchronizing Creativity with Content Management

990

Published on

Boston University began tinkering with WordPress in 2007. Today our highly customized web-publishing platform serves 1,000+ websites, ranging from blogs to behemoths, and 60+ themes, ranging from …

Boston University began tinkering with WordPress in 2007. Today our highly customized web-publishing platform serves 1,000+ websites, ranging from blogs to behemoths, and 60+ themes, ranging from bespoke to basic.

BU’s culture of free thought extends to the creative team and has lead to increasingly diverse site designs. But how do we sustain the creation of inventive visitor experiences without overcomplicating content management?

Learn about the smart choices and stupid mistakes – both creative and technical — we’ve made along the way to building the most ambitious WordPress installation in HigherEd.

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
990
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SynchronizingCreativity+ ContentManagement
  • 2. (alternate title)Designervs Developer
  • 3. (alternate title)Smartvs Stupid
  • 4. THE Con lict!
  • 5. roles executive designer editor developer help desk
  • 6. The executive needs:Value, reliabilityBUT! high output
  • 7. The help desk needs:DetaileddocumentationBUT! quick tasks
  • 8. The editor needs:Ease-of-useBUT! more features
  • 9. The developer needs:Features to buildBUT! lean codebase
  • 10. The designer needs:Total freedomBUT! quick builds
  • 11. regularity/creativity
  • 12. Meddling withWordPress& the organizational divide
  • 13. WordPress isa service foreveryone IS&T/MarCom WordPress is for big sites only2007 2008 2009 2010 2011 2012
  • 14. Pilot #1: School of Medicine= 1 designer= 0 developers= 0 editors2007 2008 2009 2010 2011 2012
  • 15. Pilot #1: School of Medicine= 1 aging CMS= 136 sites> 200 editors2007 2008 2009 2010 2011 2012
  • 16. Implementation> 1 year later= 0 designers= 0 editors= 0 sysadmins= 2 developers2007 2008 2009 2010 2011 2012
  • 17. Crippling WordPress- Comments- Roles- Categories- Tags2007 2008 2009 2010 2011 2012
  • 18. “Dont ight WordPress. Understand it. Embrace it.”
  • 19. Pilot #2: Admissions> 9.5 million views2007 2008 2009 2010 2011 2012
  • 20. Pilot #2: Admissions= 2 designers= 1 contractor= 0 IS&T2007 2008 2009 2010 2011 2012
  • 21. Pilot #3: Human Resources= 3.2 million views2007 2008 2009 2010 2011 2012
  • 22. Pilot #3: Human Resources= 2 students= 2 IS&T plugins2007 2008 2009 2010 2011 2012
  • 23. DIY themes:= 1/8 designer= 1 developer= 0 coordination2007 2008 2009 2010 2011 2012
  • 24. 581 sites 342 sites 141 sites 136 sites0 sites 2007 2008 2009 2010 2011 2012
  • 25. Total:+ 253 In-progress+ 1,800 Blogs= 2,732 Sites2007 2008 2009 2010 2011 2012
  • 26. Average Rate since 2008:= 1.9 Sites/Day!!12007 2008 2009 2010 2011 2012
  • 27. The Oh Sh*t!Moment
  • 28. roles executive designer editor developer help desk
  • 29. roles mustunderstandeach others executive designer editor developer help desk
  • 30. content design site tools
  • 31. Collaboration
  • 32. A range of offerings:1. Fully custom2. Quick setup3. DIY tools
  • 33. Can’t supportEffort & cost: 2,732 Custom Sites!1. High2. Moderate3. Low
  • 34. Establish work lows:1. Sandbox2. SVN >10,000 commits!3. Documentation4. Tools to talk
  • 35. Moving code sandbox devl pre-prod prod
  • 36. Moving content live prod content design sandbox + develop around real contentin-progress pre-prod content
  • 37. assemble teams that cross boundaries (even if it’s awkward)
  • 38. tools CUSDIYsites TOM sites lexible theme framework
  • 39. “ lexi”
  • 40. lexi= color options
  • 41. lexi+ content banner
  • 42. lexi+ layout editor
  • 43. lexi+ automated setup+ good defaults= happy help desk
  • 44. lexi logo variations
  • 45. lexi= child themes+ extensible (+/-)+ widget formats+ shortcode library
  • 46. lexi+ mobile themes
  • 47. + plugins
  • 48. How many plugins does it take?Main Main IntegratedThird-Party BU-speci ic w/ BU appsGravity Forms BU Navigation BU CalendarWP SuperCache Access Control List BU Maps (w/ Single Sign-on)Akismet Google Search User Management ApplianceNetworks for (w/ Single Sign-on)WordPress Course Feeds Content Banner Training Manager Post Details Emergency Alert Advanced Tiny MCE Site Manager Cache / Message Queue Daemon
  • 49. How many plugins does it take?Main Main IntegratedThird-Party BU-speci ic w/ BU appsGravity Forms BU Navigation BU CalendarWP SuperCache Access Control List BU Maps (w/ Single Sign-on)Akismet Google Search User Management ApplianceNetworks for (w/ Single Sign-on)WordPress Course Feeds Content Banner Training Manager Post Details Emergency Alert Advanced Tiny MCE Site Manager Cache / Message Queue Daemon
  • 50. How many plugins does it take?Main Main IntegratedThird-Party BU-speci ic w/ BU appsGravity Forms BU Navigation BU CalendarWP SuperCache Access Control List BU Maps (w/ Single Sign-on)Akismet Google Search User Management ApplianceNetworks for (w/ Single Sign-on)WordPress Course Feeds Content Banner Training Manager Post Details Emergency Alert Advanced Tiny MCE Site Manager Cache / Message Queue Daemon
  • 51. Up next» + mobile + BU Today + libraries + magazines + responsive + wp community
  • 52. (by) @gcorneGregory Corneliusvs Scott Dasse

×