Once we've done our analysis and started the project planning, Fending Group code ninjas kick into high gear. We practice continuous integration and iterative documentation. We use open source tools and platforms as much as possible, reinforcing the firm's belief in the empowerment that these technologies embody.
drupal
A lot of development and marketing firms do Drupal projects. Why wouldn't they? It's really quite easy to configure a base installation and download modules to extend the framework. But what if you need to actually do something specific with Drupal? Just because community-contributed modules can't do something well doesn't mean that *Drupal* can't do it. It might mean that you shouldn't be doing it, sure. But if an analysis turns up that Drupal fits the bill at a high level, it's likely that custom module development can get your business where you want it to be.
When considering firms, ask how engaged their principals are in the Drupal.org community, publicly contributing and reviewing code, participating in the discussions that move Drupal forward, attending and sponsoring events, and belonging to the Drupal Association. These are all part of being good Drupal citizens, proving that it's not "yet another competency", and - above all - knowing where we've been so we can create the future. Fending Group is part of that future.
