Drupal was on my radar since August, when I went to Drupal Camp CT. (Read about those experiences here.) After camp, Life got in the way, so any tinkering with Drupal was put off to the side….for over six months. With the ALA Elections coming (psst…I’m running for ALA Council with these awesome folk), and feeling inspired after learning Github*, now felt as good of a time as any to get back into Drupal.
I had a local server and installation complete from Drupal Camp CT, which made the learning process easier – the back end was all finished. In the space of two days, I had some modules and themes installed, customized the theme I chose for the final site to my liking, most of my content from my old site imported and streamlined, and the site residing on a local LAMP server we made from a desktop PC I received in an office computer lottery.
You will see now that if you go to katekosturski.com, it redirects to this blog. Later this week, I will be registering katekosturski.net as a domain, and katekosturski.com will redirect there. (I paid for katekosturski.com for two years through Weebly, and still have a year to go on the plan – easier for me to redirect than try to figure out how to cancel. Plus, a whole bunch of business cards with katekosturski.com and a conference looming means we think of something quick and dirty.)
Here’s a sneak peek:
The new main page
The landing page for all my projects, before and after library school
Sample project page (from one of my library school courses)
The list of technology competencies that keeps getting longer and longer…
The Contact Me Page
Lessons learned from this very intense course:
- Writing down your passwords is not always necessarily a bad thing. Doing the local (XAMPP on the Macbook Pro) to the LAMP server migration was tough, because I did not remember what my XAMPP database login and passwords were. We were able to get this completed thanks to the Drupal Backup and Migrate module. (Did I write down the login information for the LAMP server? Yes.) Using a service like LastPass is also on my shortlist, just in case the notebook gets damaged or destroyed.
- Installing a rich text editor should be the first thing you do. It makes creating and migrating content so much easier. I know HTML tags, but they take time to type out, and then you have to worry about ensuring tags are nested and closed properly.
- You will come up with one way to organize your content, then scrap it for another, and then another, and then another. The screenshots above are from iteration #3 of the site.
- Themes. Oh Themes. All the themes. Looking at all the themes (462 for Drupal 7 alone) is like going down a rabbit hole, but absolutely necessary to find the ideal theme for your site, one that combines functionality and usability with appearance. It took me about 20 tries before I settled on the right theme – and even that required some customizing – I didn’t like the original font, and with a little knowledge of cascading style sheets (CSS), I got it looking the way I wanted.
Would I recommend learning Drupal? Yes. You may not be able to pick it up in a weekend – some people call the learning curve a learning cliff. The best ways to learn it are to (a) attend a local Drupal Camp or Drupal meetup, and (b) just go in and play around, break things. If you really need a quick and dirty Drupal solution, Drupal Gardens is the way to go.
I know I’ve only scratched the surface with Drupal. More experimentation to come.
* Thanks to Andromeda Yelton, who causes trouble in a good way. By the way, did you know she’s running for LITA Board? You should go vote for her. Also, she built this which is just full of adorableness and tell you LITA members and prospective members how you can get involved.