Drupal

There's a little controversy in the Drupal world, a fork by Nathan Haug, aka QuickSketch. Last week he tweeted:

Results. Return On Investment. Value. How do you measure these things in a website? There's one thing you can easily measure -- cost. Or at least the amount you actually spend to build and maintain a site. The others are far more troublesome to measure.

If there's one thing that's constant in the web world, it's change.

If you've used a web ontology before, or any other large-scale data repository, you're likely familiar with one of the chief concerns facing anyone in such a position: how do you get your data into the system? Moreover, how do you get large amounts of data into the system with (relative) ease? And if you've used a content management system before, you've likely faced a similar, albeit inverted problem: how do you get your data out?

If you can accomplish these preliminary items without a good deal of effort, you're finally left with the task of transforming the data from one, and allowing it to be recognizable by the other.

If, instead, you haven't used either of these, you're likely wondering why on Earth you would want to.

I was talking with a new client the other day who spends a lot of money on Search Engine Optimization (SEO) and Search Engine Marketing (SEM) to try to get people to visit his online store. And yet his blog -- what search engines value most -- was on wordpress.com.

We're super stoked to see some press coverage of all the hard work we've been doing for the past few years!

At Freelock, we've been adopting a pattern for git branch management called Git Flow. If you haven't run across git flow before, go check out this article to get the basic concepts: A successful Git branching model.

Robyn asks:

I'm having a lot of discussions about CRM systems these days. What is CRM? To hear many talk about it, it's some magical program you buy and suddenly you start getting more business.

Drupal is one of the most popular free and open source web application frameworks. Drupal is almost infinitely extensible through not only various theme possibilities but also the vast library of modules or add-ons. However, this great extensibility is also a point of weakness should insecure or vulnerable code be used in either themes or community contributed modules that can result in compromise. The following guide on best practices for Drupal covers main areas of attention in regards to security for any Drupal web administrator.

As part of our recent site upgrade from Drupal 6 to Drupal 7, we had a bunch of content profiles to clean up.