I can smell your CMS
•
20 recomendaciones•17,999 vistas
The word is getting out. Great web site experiences require careful development and crafty execution in the front end. Squeezing every drop of performance out of your user's browser is tough, but Steve Souders and friends have mobilized an army, and we are all having a bloody good go. But there is a common threat to doing great work in the front-end. It lurks in the back-end and clients love it. It's the content management system, and more often than not, it stinks. We'll look at examples of the damaging traces CMSs leave behind in the front-end and at how we might work to reduce them. We'll find ways to fight for what matters in a CMS, and ways to avoid the smell of your CMS wafting over to the user and sacrificing the craftsmanship of good front-end engineering. Find video of this presentation
Recomendados
Recomendados
Más contenido relacionado
Similar a I can smell your CMS
Similar a I can smell your CMS (20)
Último
Último (20)
I can smell your CMS
- 1. #SMELLCMS
- 3. I CAN SMELL YOUR CMS ~
- 5. 1. AMAZING SPEAKERS 2. YOU HAVE OPTIONS 3. TALKING ABOUT CMS du l l u ll dull d @PHILHAWKSWORTH # HTML5DEVCONF
- 10. AGENCIES have a DILEMA @PHILHAWKSWORTH # HTML5DEVCONF
- 11. AGENCIES have a PROBLEM @PHILHAWKSWORTH # HTML5DEVCONF
- 14. AGENCY GAP @PHILHAWKSWORTH # HTML5DEVCONF
- 15. GIVE THEM WANT what they @PHILHAWKSWORTH # HTML5DEVCONF
- 16. GIVE THEM NEED what they @PHILHAWKSWORTH # HTML5DEVCONF
- 18. AGENCY ~ RESPONSIBILITY @PHILHAWKSWORTH # HTML5DEVCONF
- 19. DEVELOPER~ RESPONSIBILITY @PHILHAWKSWORTH # HTML5DEVCONF
- 20. BIG BRANDS STAGE AUDIENCE @PHILHAWKSWORTH # HTML5DEVCONF
- 22. @PHILHAWKSWORTH # HTML5DEVCONF GROLSCH.COM
- 23. @PHILHAWKSWORTH # HTML5DEVCONF BEETLE.COM
- 24. @PHILHAWKSWORTH # HTML5DEVCONF MCDONALDS.CO.UK
- 25. 38.28 MB 405 HTTP REQUESTS 1.1 MINUTE ONLOAD @PHILHAWKSWORTH # HTML5DEVCONF
- 27. LEARN by EXAMPLE @PHILHAWKSWORTH # HTML5DEVCONF
- 29. @PHILHAWKSWORTH # HTML5DEVCONF MILWAUKEEPOLICENEWS.COM
- 31. @PHILHAWKSWORTH # HTML5DEVCONF
- 32. LEARN by EXAMPLE @PHILHAWKSWORTH # HTML5DEVCONF
- 33. CODE is CRAFT @PHILHAWKSWORTH # HTML5DEVCONF
- 35. AVOID ~ LOCK-IN @PHILHAWKSWORTH # HTML5DEVCONF
- 38. CMS
- 39. O RLY? @PHILHAWKSWORTH # HTML5DEVCONF
- 40. THE CMS ~ PARADOX @PHILHAWKSWORTH # HTML5DEVCONF
- 41. ENTERPRISE LEVEL ~ @PHILHAWKSWORTH # HTML5DEVCONF
- 42. REASSURINGLY ~ EXPENSIVE @PHILHAWKSWORTH # HTML5DEVCONF
- 44. FLEXIBILITY does not give FLEXIBILITY @PHILHAWKSWORTH # HTML5DEVCONF
- 45. CHOICE ~ PARALYSIS
- 46. COST OF SYSTEM proportional to COST OF CHANGES @PHILHAWKSWORTH # HTML5DEVCONF
- 47. POWERFUL WORKFLOW @PHILHAWKSWORTH # HTML5DEVCONF
- 48. POWERFUL WORKFLOW versus GETTING SHIT DONE @PHILHAWKSWORTH # HTML5DEVCONF
- 49. CEO / CMO / CTO INTERN or DEVELOPER @PHILHAWKSWORTH # HTML5DEVCONF
- 51. CODE SMELL @PHILHAWKSWORTH # HTML5DEVCONF
- 52. symptom in the source code that possibly indicates a deeper problem @PHILHAWKSWORTH # HTML5DEVCONF
- 53. CMS SMELL @PHILHAWKSWORTH # HTML5DEVCONF
- 54. CMS STINK @PHILHAWKSWORTH # HTML5DEVCONF
- 55. EXAMPLES STINK of @PHILHAWKSWORTH # HTML5DEVCONF
- 56. .html .shtml .pl .php .jsp .asp .aspx @PHILHAWKSWORTH # HTML5DEVCONF
- 57. CONTENT .html .shtml .pl .php .jsp COUPLED to the .asp .aspx TECHNOLOGY @PHILHAWKSWORTH # HTML5DEVCONF
- 58. TIMBL SAYS
- 59. LOCK IN
- 67. ENTERPRISE LEVEL ~ @PHILHAWKSWORTH #HTML5DEVCONF
- 68. ENTERPRISE level FACEPALM @PHILHAWKSWORTH #HTML5DEVCONF
- 70. LOCK IN
- 71. FUGLY
- 72. URL DESIGN CRAFT @PHILHAWKSWORTH # HTML5DEVCONF
- 73. MAKE URL DESIGN A PRIORITY @PHILHAWKSWORTH # HTML5DEVCONF
- 74. tip URL STABILITY @PHILHAWKSWORTH # HTML5DEVCONF
- 75. tip SIREN OF SOCIAL MEDIA @PHILHAWKSWORTH # HTML5DEVCONF
- 76. tip FACEBOOK LIKES @PHILHAWKSWORTH # HTML5DEVCONF
- 78. @PHILHAWKSWORTH # HTML5DEVCONF STEVE SOUDERS
- 79. OPTIMISATION
- 80. OPTIMISATION
- 81. TUNING OPTIMISATIONS TRICKS CRAFT CMS ~ @PHILHAWKSWORTH # HTML5DEVCONF
- 82. .net BURP @PHILHAWKSWORTH # HTML5DEVCONF
- 83. UI HOOKS @PHILHAWKSWORTH # HTML5DEVCONF
- 84. CLASSIC STINK @PHILHAWKSWORTH # HTML5DEVCONF
- 85. MODULARITY & FLEXIBILITY @PHILHAWKSWORTH # HTML5DEVCONF
- 86. A GOOD THING @PHILHAWKSWORTH #HTML5DEVCONF
- 87. O RLY? @PHILHAWKSWORTH # HTML5DEVCONF
- 88. A MODULE / HTML TARGET CSS JAVASCRIPT @PHILHAWKSWORTH # HTML5DEVCONF
- 89. A MODULE / HTML TARGET CSS JAVASCRIPT / ENCAPSULATED REPEATABLE @PHILHAWKSWORTH # HTML5DEVCONF
- 90. A MODULE / HTML TARGET CSS JAVASCRIPT / ENCAPSULATED REPEATABLE @PHILHAWKSWORTH # HTML5DEVCONF
- 93. KILLS ~ RENDERING PERFORMANCE @PHILHAWKSWORTH # HTML5DEVCONF
- 94. MAINTENANCE ~ NIGHTMARE @PHILHAWKSWORTH # HTML5DEVCONF
- 95. STINK
- 96. MAKES SOUDERS CRY @PHILHAWKSWORTH # HTML5DEVCONF
- 97. THOU SHALT NOT MAKE SOUDERS CRY @PHILHAWKSWORTH # HTML5DEVCONF
- 98. @PHILHAWKSWORTH # HTML5DEVCONF AMAZING DESIGNERS
- 99. DESIGN EXPERTISE @PHILHAWKSWORTH # HTML5DEVCONF
- 100. CORE FEATURE @PHILHAWKSWORTH # HTML5DEVCONF
- 102. WYSIWYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 103. WYSIWYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 104. WYSIWYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 105. WYSIWYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 106. WYSIWYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 107. WYSIwYG DANGER @PHILHAWKSWORTH #HTML5DEVCONF
- 108. WYSIWY G $ @PHILHAWKSWOR #HTML5DEVCONF TH
- 109. WYSIWYG
- 110. WYSIWYGITE
- 112. WYSIWTF
- 113. PROTECT the MARKUP @PHILHAWKSWORTH # HTML5DEVCONF
- 114. <p class="footnote"><font size="4"> </font></p> <p class="footnote"> please <a style="COLOR: #4b7228" onclick="javascript:popup('/list.html','','860','900');" href="javascript: void(0);"> <font color="#000000"><strong>click</strong></font> <font color="#000000"><strong>here</strong></font> </a> to add join our waiting list. </p> <p class="footnote"> <em>• <a href="/Cancellation">Cancellation Policy</a></em> </p> <p class="footnote"> <em></em> </p> @PHILHAWKSWORTH # HTML5DEVCONF
- 115. <p class="footnote"> </p> <p class="footnote"><strong></strong><strong></strong> </p> <p class="footnote"> </p> <p class="footnote"> </p> <p class="footnote"> </p> <p class="footnote"> </p> <p class="footnote"> </p> <p class="footnote"><strong></strong> </p> <p class="footnote"> </p> @PHILHAWKSWORTH # HTML5DEVCONF
- 116. STINK
- 117. ROUND TRIPPING @PHILHAWKSWORTH # HTML5DEVCONF
- 118. CIRCULAR STINK
- 120. STRUCTURED CONTENT CHANGE @PHILHAWKSWORTH # HTML5DEVCONF
- 121. MANAGE CONTENT not DESIGN @PHILHAWKSWORTH # HTML5DEVCONF
- 122. AVOID ~ LOCK-IN @PHILHAWKSWORTH # HTML5DEVCONF
- 123. TEACH A MAN TO FISH @PHILHAWKSWORTH # HTML5DEVCONF
- 124. HOST A BBQ @PHILHAWKSWORTH # HTML5DEVCONF http://www.flickr.com/photos/cmbellman/2576196608/
- 125. RESEARCH PAPERS ON INTENSIVE SALMON FARMING @PHILHAWKSWORTH # HTML5DEVCONF
- 127. BAD SAUSAGES @PHILHAWKSWORTH # HTML5DEVCONF
- 128. CHALLENGING the INTRODUCTION OF STINK @PHILHAWKSWORTH #HTML5DEVCONF
- 129. CONSTRAINTS CAN BE ENABLERS @PHILHAWKSWORTH # HTML5DEVCONF
- 131. CHOICE ~ PARALYSIS
- 132. OUR CMS DOESN’T SUPPORT MOBILE WTF? @PHILHAWKSWORTH # HTML5DEVCONF
- 133. ...MOBILE MODULE CAN BE PURCHASED @PHILHAWKSWORTH # HTML5DEVCONF
- 134. ENTERPRISE level FACEPALM @PHILHAWKSWORTH # HTML5DEVCONF
- 135. MANAGE CONTENT not DESIGN @PHILHAWKSWORTH # HTML5DEVCONF
- 136. FUTURE FRIENDLY @PHILHAWKSWORTH # HTML5DEVCONF
- 138. WHAT CONTENT NEEDS to be DYNAMIC? @PHILHAWKSWORTH # HTML5DEVCONF
- 139. WHAT CONTENT REALLY NEEDS to be DYNAMIC? @PHILHAWKSWORTH # HTML5DEVCONF
- 141. ONE DAY, WE MIGHT WANT TO... @PHILHAWKSWORTH # HTML5DEVCONF
- 143. RUTHLESSLY PURSUE SIMPLICITY @PHILHAWKSWORTH # HTML5DEVCONF
- 144. AVAILABLE SKILLS ~ @PHILHAWKSWORTH # HTML5DEVCONF
- 145. CEO / CMO / CTO INTERN or DEVELOPER @PHILHAWKSWORTH # HTML5DEVCONF
- 147. HTML > COMPLEX CMS @PHILHAWKSWORTH # HTML5DEVCONF
- 148. DEV > COMPLEX CMS @PHILHAWKSWORTH # HTML5DEVCONF
- 149. AVOID LOCK IN
- 150. CONSIDER ~ NOCMS @PHILHAWKSWORTH # HTML5DEVCONF
- 151. TOOLS CONVENTIONS PATTERNS GUIDANCE TEMPLATING @PHILHAWKSWORTH # HTML5DEVCONF
- 152. JEKYLL github.com/mojombo/jekyll
- 153. PERCH grabaperch.com
- 154. OPTIMISATION
- 155. COMMON AGENCY APPROACH @PHILHAWKSWORTH # HTML5DEVCONF
- 157. USER EXPERIENCE DESIGN F/E DEV INTEGRATION @PHILHAWKSWORTH # HTML5DEVCONF
- 158. USER EXPERIENCE DESIGN F/E DEV INTEGRATION @PHILHAWKSWORTH # HTML5DEVCONF
- 159. @PHILHAWKSWORTH # HTML5DEVCONF TO FINISH
- 160. CHALLENGE ~ CMS STINK @PHILHAWKSWORTH # HTML5DEVCONF
- 161. PROTECT YOUR ~ CRAFT @PHILHAWKSWORTH # HTML5DEVCONF
- 162. FIGHT FOR THE CHANCE TO DO GOOD ON THE WEB @PHILHAWKSWORTH # HTML5DEVCONF
- 163. THANKS http://stephenwaller.tumblr.com http://www.flickr.com/photos/employtheskinnyboy/3523608412 http://www.flickr.com/photos/bredgur/1323025528 http://www.flickr.com/photos/ansik/3033147092 http://www.flickr.com/photos/globevisions/2057289060 http://www.flickr.com/photos/cmbellman/2576196608 http://www.flickr.com/photos/ipeat/1492127164 http://www.flickr.com/photos/adamkjems/3559454088 http://www.flickr.com/photos/floradora1 http://www.flickr.com/photos/flowercat/2723867176 http://www.flickr.com/photos/timdrivas/6891133167 http://www.flickr.com/photos/gasi/1418791186 LINKS http://hawksworx.com http://grabaperch.com http://github.com/mojombo/jekyll http://www.rachelandrew.co.uk/archives/2012/09/21/we-need-to-talk-about-content-management @PHILHAWKSWORTH # HTML5DEVCONF