Skip directly to content

Why a CMS? Why Drupal?

on Mon, 07/13/2015 - 18:05

The proposal on the table is to pack in our static HTML site and move to a CMS (Content Managment System)

Why a CMS?

  1. One stop destination: A decent CMS can have static pages, blogs, forums, embed google docs (eg our current inventory), calendars (eg shift calendar), galleries, multilingual support, slide shows, etc, etc. No need for multiple sites hosting seperate functions.
  2. Multiple authors: Once the site is set up we don't have the bottle neck of one or two site admins who need HTML & FTP skills to maintain the site. Instead we can designate as many contributors as we like to post log updates, blog entries, photos, news items, useful resources for bikies, etc.
  3. Ease of use: Except for significant changes to the site structure or appearance most contributors don't need any more computer skills than they already have for writing Word docs and posting pictures to their Facebook account.
  4. Dynamic: With multiple authors it is easier to have constant new content to keep the site interesting and worth visting. For eg why would anyone who has seen our current site twice ever visit it a third time?
  5. Autonomy: With a CMS it is not too complicated to add or remove functionality, or to move the site to a different provider/server whenever it is to our advantage to do so;
  6. Security. The entire CMS can be backed up and moved as needed. No risk of losing everything because for eg a particular forum provider went out of business.
  7. Other?

Why Drupal?

  1. Free: It's Open Source (as are many others)
  2. Ease: The Drupal core is pretty stripped down, clean and uncomplicated. Others are even cleaner (eg WordPress), however;
  3. Versatility: Drupal has hundreds of modules you can add on if you want a particular functionality. The real danger with Drupal is too many people get function happy and create sprawling monsters that are hard to maintain, but as long as an organization stays focused on what it needs this is not a problem;
  4. Support. The Drupal community if HUGE with thousands of developers working on it all the time. It is secure, stable (ie not going away) and current.
  5. Well Known: With so many Drupal sites and users even Drupal Admin skills are fairly common. At least one of our volunteers is even a Drupal programmer;
  6. This site exists: To demonstrate the advantages of a CMS I started to create this site. With one thing and another it is now largely done. Go Figure. So Please have a look around the site and see what you think. Offer any condemnation/praise/comments/other in comments to this post.
  7. Other?

Why Drupal Gardens?

  1. Ease: Acquia is the premier Drupal hoster. Thier coders keep the core application up to date and debugged.
  2. Security: They handle the security updates, bug fixes, and back ups
  3. Stable: They have been around a long time and don't look like they are going anywhere.
  4. Affordable: For a bit over $100/yr they do all of the above and host the site. We jsut worry about content.
  5. Other?
greenfyre's picture

8. With a CMS clients could be directed to post their questions to a forum rather than an email where the next Recyclore person who logs on could answer them which would mean answering them could be shared (right now it is a significant load that all falls on one person).

healer's picture

If others agree to this too then what's the next steps to migrate to it? Below are a few potential ideas.

  1. Training for admins
    1. What does it do? What else can it do?
    2. Diff roles (admins, volunteers, visitors, ...?)
    3. How to...
    4. Backing up & restoring content
    5. Staff turnover
    6. Where to go for more info/training?
  2. Add essential content (anything else from current site? Admin space with imbedded Google Docs files?)
  3. Test features & usability
  4. Buy year subscription to move our domain
  5. Move domain
  6. Promote
  7. Decommision old site