Drupal deployment with Git Flow
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.
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.
In the software industry, the definition of "success" isn't necessarily the same as it is for the rest of the world. The customer asks for a complex system composed of many parts, with a specified budget, and a timeline. A software project is usually considered successful if any part of the system is developed, at any cost, at some time. Not necessarily the functionality requested, the budget, or the deadline.
So claimed Steve McConnell at a recent talk about the business value of software processes Timon and I attended.
As part of our recent site upgrade from Drupal 6 to Drupal 7, we had a bunch of content profiles to clean up.
Over the past couple weeks, I've updated the Drupal Dojo Toolkit module to support the new AMD module layout and asynchronous loading.
Via the Seattle Tech Startups list, I came across probably the most vehement, well-written, detailed critique of the PHP language I have seen yet.
We've had several clients recently chafing at how confining Drupal sites can be -- it can be a lot more work to make individual pages vary from the template, and if you have build web sites using a tool like Dreamweaver, you can't tweak the layout the same way.
A couple weeks ago I wrote a post on why customers complain about Drupal -- the short version is that they either had incorrect expectations, or "developers" who were in over their heads.
February 2010
Did you notice? The world's a different place. Rules for doing business have changed—there's new ways of getting hired, finding employees, reaching new customers, and (shudder) for them to reach you. Economies of scale have flipped—it's getting more expensive to do things on a huge scale, and far cheaper to do them at a micro scale. Mass market items have lost their appeal, and people yearn for authentic, individual connections in a world of franchise same-ness.
"I just want a simple, static website."
OK. Why?
"I don't want to spend the extra money on a CMS. I don't have time to manage a site. I don't know HTML. I just want something quick."
OK.
I get this question all the time: What's the difference between Drupal and Ruby on Rails, or another framework?
At Freelock, we're big fans of the Dojo Toolkit. It's a Javascript library for providing data-backed widgets in web applications, on-the-fly graphing, animations, and much more.