We always have had WordPress sites in our client portfolio and have had a very unique history of watching both WordPress and Drupal evolve. Today, we’re an Acquia partner and spend our conference time at DrupalCons. That is when we started developing sites with Drupal. We hit up all of the WordCamps that we could, and even hung out at the Automattic office, back when it was on the unstable pier in San Francisco.Īlong the way, our client roster grew and we encountered needs for more content types, a richer admin experience, and a more Enterprise Level CMS. ![]() We were active in the WordPress community and were at the original WordCamp San Diego planning meeting. It was such an easy to use platform, for both content editors as well as for developers. The saying is very true “if the only tool you have is a hammer, everything starts looking like a nail”. Note: we often refer to the “admin” as the password protected web portal where clients update their content. The sites that we were developing had very minimal content types and the general WordPress page content block was sufficient to give our clients a clean page admin experience. At that time, these sites were smaller and WordPress was evolving from a blogging platform to a full fledged content management system (CMS). When we first started developing sites in 2007, every site we built was with WordPress. This article is updated frequently as we hands on uncover differences between WordPress or Drupal. This article was originally published in 2011 and has been updated for 12 years now! Some web development best practices, or rather, common practices, have changed during that time.
0 Comments
Leave a Reply. |