Choosing the "right" CMS
17 likes5,529 views
The document discusses the challenges of choosing a content management system (CMS) for web development, emphasizing the importance of understanding the implications of open source versus proprietary solutions. It highlights various factors to consider, such as costs, user experience, multilingual needs, and vendor support. The author expresses a desire for more awareness among developers regarding their influence on newcomers in the field.
Choosing the "right" CMS
- 1. SALLY JENKINSON · @sjenkinson · East Digital · 9th April 2015 “right” cms Choosing the
- 2. Hello! SALLY JENKINSON Freelance technical consultant & solutions architect ! @sjenkinson sally@recordssoundthesame.com recordssoundthesame.com
- 8. Choosing a Content management system
- 13. As a new developer, I am easily swayed by the opinions of people I respect, or at least view as more experienced. This post was kicked off by a few back and forth tweets on open source contributions. 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
- 15. THE agency should always decide
- 17. 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
- 20. When you don’t understand your CMS… ! @hugorifkind
- 21. THE product can do everything
- 23. everyone else is using it
- 25. Is bespoke best?
- 29. No CMS?
- 31. How do I choose the right cms?
- 33. Features 1. Costs Open source vs proprietary Development impact
- 34. Impact on other technical elements 2. Experience of users Level of complexity Integration considerations
- 35. Introducing constraints 3. Multilingual needs Product confidence & vision Editor usage scenarios
- 36. Migration and data assessment 4. Vendor support Concurrent admin users
- 37. “It depends” - Every web professional, ever