SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Talk given at Front-end London on the 28th May 2015
Digital projects involve a great deal of choices around products and technologies, with a content management system often being integral. Using this scenario, we’ll explore certain pitfalls around selecting technology for the wrong reasons and discuss important questions that should be considered before choices are made.
Talk given at Front-end London on the 28th May 2015
Digital projects involve a great deal of choices around products and technologies, with a content management system often being integral. Using this scenario, we’ll explore certain pitfalls around selecting technology for the wrong reasons and discuss important questions that should be considered before choices are made.
As a new developer, I
am easily swayed by the opinions of people I respect, or at least view as more experienced. […] ! One person stated that I don’t need to worry about making open source contributions and I went “Yay, cool, less pressure”, another seemed to state that I am of little worth if I don’t contribute “Fuck, okay, I guess I better get on that then”. I wish programmers were more aware of the things they are saying and the attitudes they express, and how that might effect a young padawan like me. Charlotte Spencer http://goo.gl/Uc2tSl @sjenkinson TIP 3: Your choices can influence others
Back in 2008 (when we
started Bearded), one of our differentiators was that we built every site on a CMS. At the time, many agencies had not-insignificant revenue streams derived from updating their clients’ site content on their behalf. ! But we didn’t want to do that work, and our clients didn’t want to pay for it. Building their site on a CMS and training them to use it was a natural solution. It solved both of our problems, recurring revenue be damned! It gave our clients power that they wanted and needed. Matt GRiffin http://goo.gl/XPM5kK @sjenkinson
Features Open source Costs KNOCK-ON
IMPACTS Complexity APPROPRIATENESS User experience/ experience of users Constraints/ flexibility Product confidence LEVEL OF CUSTOMISATION NEEDED fit with your overall architecture migration vendor support @sjenkinson