Author
Juan Andrés ZeniJuan Andres is the SRE Studio Lead at Moove It, where he works in the design and implementation of fault-tolerant, cost-efficient, and resilient architectures in the cloud for agile software projects.
DevSnack #37: Deciding whether to use a platform for managing the content of a website is a decisive choice to make at the beginning of a web project. We should consider time, budget and client flexibility around requirements. Today’s DevSnack will explore when it’s convenient to use a Content Management System (CMS), and will present some options available in the market.
# 1 – When use a CMS?
In this article, @joshuakrohn describes those situations where it’s convenient to use a CMS based on the specifics of the project. For blogs, sites of news or e-commerce portals, given that the content needs to be updated frequently, a CMS is useful. Not using a CMS probably means that the user should edit the source code each time he want to publish new content.
# 2 – Why use a CMS?
In this post, @Jeff_A_Kline lists some of the benefits of using a CMS in a web project. He highlights that the content is an independent layer to the design, so when a redesign is needed the work is much easier. He also points up that the access to most up-to-date features on the market usually are just one update away.
# 3 – How CMS works
This link is a great resource for understanding how Content Management Sytems works. It briefly explains how the actors (users) participate in the updating process, and highlight how the webmaster is not involved.
#4 – Scrivito, a CMS for Ruby on Rails Projects
The market is full of options, but none of them are based on Ruby on Rails. Scrivito is the first-ever 100% Ruby on Rails CMS solution to not only meet but surpass the feature sets of WordPress or Drupal. Lack of features is consistently among the top reasons given by Ruby on Rails developers for choosing WordPress over a Ruby CMS. By delivering WYSIWYG editing, large asset management support, plus all the benefits of the cloud, Scrivito is simply the best Ruby CMS on the market today.
# 5 – Thinking on coding you own CMS?
In this article @danielthrelfall analyzes the cost of creating your own CMS. The author also evaluates the possibility of modifying an existent CMS and customizing it according to the needs of the project, in order to optimize the development time and the quality of the the product.
DevSnack by Moove-it is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
