Language Selection

English French German Italian Portuguese Spanish

Open Source Content Management Set Up

Filed under
Web

OpensourceCMS.com has been around since August 2002. Founder Scott Goodwin was an entrepreneur and M.B.A graduate before he started playing with content management systems.

What is your story Scott?

In 2002 I stumbled upon open source CMS's quite by accident. I had no idea these systems were available for free. I found that many of the official CMS sites didn't have demos of their creations. Thus, you had to install each one to see if you liked it or not. This was extremely time consuming and frustrating.

I thought there should be a site that allows people to "test drive" many of the best systems vailable. Since there was no site like that, I started opensourceCMS.com. I had no grand business model. I just thought a site like this would be useful.

Full Article


More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more