In the past year, we've worked with a number of fantastic clients. One of the things we've seen repeatedly is a desire by some clients to do work that is a "port" of the existing site to Drupal technologies. This is often not the right approach.
In the past year, we've worked with a number of fantastic clients. One of the things we've seen repeatedly is a desire by some clients to do work that is a "port" of the existing site to Drupal technologies. This is often not the right approach.
Over the course of our search for new developers for WorkHabit, I've often gotten a letter or message from Drupal Zealots large and small -- Drupal developers that were born and indoctrinated into the community and believe it's the best thing since sliced bread.
Drupal as a framework doesn't always lend itself well to detailed specifications — and many projects try very hard to do them to "contain risk" and get "a clear and exact" deliverable.
Sometimes an afterthought, sometimes the only good-looking page on a site: registration pages are the heart and soul of user participation.
I've taken a couple of days off to watch the outcome of the Cloud Expo, CloudCamp, and especially, the CCIF meetings. After three days, this posting is my response to everything I learned, and what I think next steps are. I'd like to have an open dialogue about it: but let's get moving.
Here's an interesting problem. Through the dot com era (and slightly before), the hosting market was driven to ravenous acquisitions of companies based on the value of their customers.
Here is a fact: developers tend to overvalue their innovations.
When users control the conversation, there is an interesting tendency for the elevation of users as experts based on contribution.
Twitter won't work with my social network, because my social network relies on keyword taxonomies. So, right now, it's easy to associate twitter with a profile, because it's a 1-1 relationship. And I can build a twitter channel (#workhabitinc) for example, to pull from multiple twitter feeds.
It seems every year there is a trend that pops up that I didn't realized was "hip" until I read it in someone else's blog. Ajax was one of those trends, a 5-6 year old technology that just blew up overnight and became a phenomenon.
When I was in high-school, I worked at an office supply chain in the "Business Machines" department. I sold computers, adding machines, Palm Pilots (the first revision!), printers, cables, you name it.
I'm writing this post to call attention to a new training event. It seems like Lullabot is once again on a training roll, with their new video and now a really interesting training event called Do It With Drupal.
Document Management has existed in many forms for decades now: Documentum, Docsys, Knowledgetree, Alfresco, and others. Most of the solutions have existed at the Enterprise level, and have had limited utility and penetration into smaller markets.
Somebody recently asked me whether I thought Drupal was a good platform for a/b Marketing. Since Drupal is such good platform for search engine optimization, many people automatically assume that Drupal is very good for doing marketing campaigns.
I don't mean to single anyone out here, but this is an excellent opportunity to single out why it's important to back up your strategies with a good technology plan.