Sorting out gemfiles

I recently came across the Aurora theme in my quest for a theme that was responsive but didn't bloat the DOM. Codekit didn't seem to want to work for this purpose, so I took the plunge into the bigboypool.

Good Progress

I've had a very productive couple of days. Yesterday I set about seeing if I could somehow tame our incredibly bad taxonomy. The problem has been that there are numerous duplicate terms that only make sense when you look at their parent terms. So I was quite stoked to find that Drupal supported duplicate terms. After that it was a matter of getting the existing terms into Drupal. As usual, my first step was to search Drupal.org for some sort of import module. Sure enough, I discovered Taxonomy CSV import/export.

Tools of the Trade

So today I was trying to make the case for getting a Mac computer instead of the crappy Windows machine I have. It's definitely a big difference between what I'm used to and government. I got so used to using a Macbook Air with Coda and my new favorite image editor, Pixelmator and today they gave me a Dell with Win7 and Adobe's CS5 package. I'm still hopeful I can get a Mac, it was something I asked about before even taking the job, so it's not completely out of the question.

New Job Started Today

Well, I started my new job today, though it was all just orientation today. I'm essentially starting this blog to document my experience migrating a major government website from the platform I've been working on for the past 8 years, Commonspot, to Drupal. I've been learning Drupal for about the last 9-10 months and I'm really enjoying it. I've only done on client site, (http://www.ucdc.edu) and I have a couple under way, but this new job will be much larger than anything I've currently done. I am looking forward to the challenge.

Great website inspiration

I always like looking at these collections of interesting web design. There's just sooo much content online, it's so hard to stay on top of the state of the art.

I wish more government agencies would do this.

http://www.consumerfinance.gov/blog/the-cfpbs-source-code-policy-open-an...

"When we build our own software or contract with a third party to build it for us, we will share the code with the public at no charge."

SInce we the people paid to have the code built, it should be a work-for-hire situation and should already belong to the American people!

Subscribe to Imagecurrency RSS