Drupal

I got a job at Acquia!

Just over 6 years ago I joined ASU's University Technology Office as a young and admittedly very inexperienced developer. I was fortunate enough to spend the time since then working for folks with foresight and strategic vision that I've only recently started to appreciate. I've also been blessed to have been involved with projects that I feel proud to say are changing the face of education. In short, I've loved my work at ASU more than my clumsy writing can describe here.

The public university system is not without its critics -- I've frequently been one of them -- but ASU is different. In my six years with ASU, I've worked with some of the most talented, dedicated, passionate, and brilliant people I could ever imagine encountering in one place. My team mates in alt^I and UTO are phenomenal. I had an incredible and rewarding few years obtaining my masters in Educational Technology, where I met folks that have changed my life and informed my vision of innovation in education. I can say the same about my friends in CLAS, the Provost Communication Group, President's Office, ASU Foundation, Education, Engineering, Nursing, and the ASU community at large.

Sometimes, though, an opportunity comes by that would be unthinkable to pass up.

In a couple of weeks, I'll start a new job at Acquia. I'm joining their team as a Technical Consultant. The role is a little hard to define without using the word "consulting," but it essentially comes down to helping customers successfully deploy and work with Drupal-based solutions. In my dealings with the Drupal community, there are only a few companies that I've ever considered to be "I would drop everything to work there" types of places, and Acquia was one of them (Yes, ASU is that great of a place). Acquia brings a passion for and focus on enterprise-level, large-scale solutions and support that melds with my vision of Drupal as a "serious" web development framework. While they see it as a long-term player in the web software market, their vision is to ensure that Drupal remains accessible and usable, and that the barrier to entry continues to lower. Most importantly, they've managed to be great contributors to the Drupal community while developing a sustainable, strategic approach to the business side of things.

I really can't describe how excited I am about this new adventure. My work at ASU has been so rewarding, but the scope of possibilities with work at Acquia is unlimited. I'm both humbled and nervous to be headed off to work with some of the best Drupal developers in the world, in a company guided by the founder of Drupal itself, Dries Buytaert. The leadership team at Acquia share a bold vision for the future of Drupal - and open source in general - one that makes me feel confident in having placed all my chips on that table several years ago.

I'm fortunate enough to be staying in Phoenix, close to my family and friends. The consultant job is going to have me traveling all over the country, though, which is something I'm really looking forward to trying out. Acquia is located in Boston, and I think it's going to be great to spend time there and other places on the east coast, which is still relatively foreign land to me. I think my upcoming travel will afford me opportunities to meet some incredible people.

ASU is a wonderful place, and I hope that I'll remain in touch and work with many of you in the future. I've made countless friends at the university and consider it "my" school, so I'll definitely not be disappearing. I will always be a Sun Devil.

How I build an Ubuntu 10.04 LTS Drupal Development VM in VirtualBox

A development virtual machine can be really handy. It gives you a sandbox of sorts where you can feel free to test and experiment knowing that in a worst-case scenario you can just delete the VM and start over. It can also be a great way to practice server configurations and sketch out "real-world" server setups. Here's the process I follow to setup my Ubuntu 10.04 LTS Drupal development VM in VirtualBox. Aside from the VM-specific steps, these instructions should work for a regular Ubuntu server (VM or not).

Decoder Ring: a framework for collaborative language research

This spring, I wrapped up my masters degree in Educational Technology at Arizona State University. In my studies, I had the great pleasure of working with some of the trailblazing academics in the field of educational language, literacy, and gaming studies. Among the folks I've interacted with over the last several years, James Paul Gee and Elisabeth Hayes have overwhelmingly influenced my interests in academic research in the field. Guided by their seminars and publications, along with many others, including Sean Duncan and Constance Steinkuehler, I developed a strong interest in utilizing my web application development skills to create tools that further the field of academic research in language and literacy.

Last fall, I started in earnest on a project to do just that and, to make a long story very short, the ultimate result is Decoder Ring, which I've just presented at the 2010 Games, Learning & Society Conference. Decoder Ring is a web-based, collaborative language analysis tool designed for academic research of textual content. It features:

  • Abstracted, flexible, powerful data model
  • Sustainable, low cost, open source framework
  • Project- and group-based to facilitate collaboration
  • Tools for gathering (scraping), importing, browsing, and exporting large data sets
  • Automated and extensible reporting tools

DrupalCon San Francisco 2010 Presentation: Drupal at ASU - Slides and video

I recently presented a session titled Case Studies in Academia: Drupal at ASU & Johns Hopkins Knowledge for Health at DrupalCon San Francisco 2010. The presentation went really well. It was great to meet with all the other universities that are using Drupal and talk about the wildly varying ways Drupal is being used in academia.

If you'd like to watch the video recording, it's available on Archive.org or on the DrupalCon presentation page. The slides for the presentation are attached below.

(Finally) rid of that ugly theme

I've hated my personal site's theme for a couple of years now. Cleaning it up has been sitting a few items down on my todo list for a long time, and I finally decided to stop waiting for a good time and just move it up the stack this week.

Old site design
Eww.

I tried out a couple of starter Drupal themes (Ninesixty and Blueprint) but found them light on documentation and simply not as "complete" as my stand-by on nearly every site, Zen. I was adventurous and went for the 6.x-2.x-dev version of Zen, which has some really nice changes under the hood. The dev branch's documentation still needs some updating, but my familiarity with the theme helped me quickly overcome any issues I encountered.

New site design
Fewer viewers report wanting to throw up in their mouths when viewing this theme.

My main goal with the new theme was to get a more clean, readable, and more timeless look. I essentially don't want to have to update my site's theme anymore... at least, not unless one of my far-more-talented-than-me graphic designer friends want to help me out with it. *wink-wink* *nudge-nudge*

I'll be going through old posts and cleaning them up as-needed to make everything fit within the new size restrictions, but that may take a few days.

[Updated] Upgrading your site to Drupal 6.x: Handout for July 2009 ASU Drupal Users Group

[Update] I've updated the handout to be a single page, cleaned-up a lot of the instruction, and fixed several typos. Please see the revised handout below.

An additional note: If you use the handout to assist your site upgrade process, please do me a favor and fill out a brief survey.

Original post:

Attached below is the handout from the July 2009 ASU Drupal Users Group workshop. Use this handout to help you cover all the steps necessary to upgrade your site from Drupal 5.x to 6.x. It contains a module inventory worksheet and a site review checklist that can be used to help you make sure your site is fully functional after the upgrade.

Note: I created this handout for the ASU DUG workshop as well as an assignment for one of the courses I'm in at ASU. If you use the handout as an aid when performing a site upgrade, please let me know so that I can send you a link to a brief survey about your experience with it. The survey will help me get a better understanding of how you used the handout and how it can be improved.

Slides for April 2009 ASU Drupal Users Group

Attached below are the slides for the April, 2009 ASU Drupal Users Group presentation I gave on maintaining sites using a combination of CVS (to checkout Drupal core and contrib modules) and Subversion (for backing up your site's code base and integrating with locally maintained modules and themes).

Here's a quick rundown of links mentioned in the presentation:

Read on after the break for code samples.

Slides for March 2009 ASU Drupal Users Group

Attached below are the slides for the March, 2009 ASU Drupal Users Group presentation I gave. The presentation contains info on the following topics:

DrupalCon 2009: Washington, DC

CAS

FeedAPI

Miscellaneous Links

Catching Apache segfaults due to eAccelerator

Last night we migrated our Linode for Gamers With Jobs to a new Xen VPS and we've noticed a significant performance boost. We did, however, start encountering a random issue with segmentation faults in Apache. If you haven't seen this happen before, it tends to begin innocently with one Apache process dying, and therefore giving errors (usually WSOD), but quickly balloons into dozens of dead processes. It essentially hoses Apache.

Apparently the issue is due to eAccelerator, so I reinstalled it and cleared its caches in the hope that it might limit its occurrence. Just in case, though, 2bits has a great fix for it, using the logwatcher script by Firebright, Inc. I was able to quickly get it going, and the only difference is that I used the Debian init.d script provided by Derek Laventure to run it.

Taxonomy Search 2.0 module release

For a project at work, we needed to be able to manage, and therefore search, large-scale taxonomies (10,000+ terms). Users needed to be able to search for term names, descriptions and synonyms, so I figured a module using the Drupal search API seemed to be the best bet for a solution. I dove in deep and came back up with Taxonomy Search 2.x.

I've just released version 2.0 of the module, and you can check it out at the Taxonomy Search project page. I'd love some feedback, as this is my first module that utilizes the search API, and there may be some rough edges. Please take a look at let me know what you think!

Syndicate content