Add new comment

A writer joins Acquia

Today marks my first day as Acquia's Director of Content and Communications, although I've been following the company since its birth. I started using Drupal in late 2007 -- right around when Jay and Dries were founding the company -- to build a site that would promote a book that was soon to be published. That site launched within a month of Acquia's first hires, and the popularity of Drupal supported me to write several video courses for lynda.com, a book about Drupal 7, and reports for Drupal-focused companies. Of course Acquia and I also contributed to issue queues, discussions, camps, and other community-based initiatives all along. We grew up together in the Drupal community, although you could say that I came to it as an immigrant, while the company is wholly native-born.

I've watched it grow with fascination. In 2008 I predicted Drupal Gardens and wrote positively about the company's future, then praised Acquia Dev Desktop as having "the potential to be a really big deal for Drupal". (I think that potential's been realized, although that handy Drupal installer never gets the attention I think it deserves.) I also wrote about how Acquia could provide documentation structure unavailable on drupal.org, which is coming true with Acquia Library.

In my new position I'll be rewriting the Acquia.com website; producing marketing materials; helping coordinate public-relations efforts; and generally defining the tone of the company's public presentation. As is the rule at Acquia, some of what I do here will be for the larger Drupal community, as materials that support events, organizations, and the project as a whole.

On that note, I'd love to hear your ideas for specific content that Acquia could produce to help Drupal in general. There are already some amazing initiatives within the community, such as the Marketing of Drupal group: I want to help Acquia supplement those activities to help us show what Drupal does, how it's succeeding in the world, and the benefits of adopting it. On that note, if you're an experienced writer who's knowledgeable about Drupal, please contact me at tom.geller at this domain. There's a lot of work to be done: Let's get started!

So: Acquia and I are all grown up now. We're the children of parents -- Drupal and its community -- who have achieved rapid, unexpected success. Having finally gotten the chance to work alongside the hundred-plus intelligent and driven people who comprise Acquia, I can't imagine a better sibling, or better parents.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.