Movable Type: An Interview with Angela Jordan of WTIU

For any of you that may not be familiar with it, Movable Type is a blogging tool--one of the first, in fact--used to run a blogging website. Therefore, I was rather surprised recently to stumble across it "powering" a public television station website, specifically WTIU in Indiana. So, I contacted their web developer, Angela Jordan, and asked her if she wouldn't mind answering a few questions for all of us about the use of Movable Type to power her station's website. She agreed, and, frankly, it's always good to yield the floor to someone smarter than me.

• ptvGuy

  • Hi, Angela, and thank you for agreeing to talk to us.

• Angela Jordan

  Hi Tim, I'm happy to get the chance to discuss this with you.

• ptvGuy

  • Well, as you know, the main reason I asked to talk to you was to find out more about your use of Movable Type, essentially a blogging tool, to power your station's website. Frankly, it's an idea that just never even occurred to me, and yet it's obviously working for your site--which looks great, by the way.

• Angela Jordan

  Thanks. The site layout is done entirely with CSS--no tables are used--so maybe that's another conversation some time if you're interested. Movable Type certainly IS a blogging tool, and that's how I first learned about it (when I set up my own blog in 2003) but, as many people have recognized, it's certainly not ONLY a blogging tool. It didn't take long to see that the software was really a powerful, and, at that time, completely free Content Management System (which, of course, is all that blogging tools really are anyway, a simple interface for getting your content onto the web.) I started imagining the possibilities and thinking "What if...?" mostly because I was spending an inordinate amount of my time as the sole web developer/designer/coder/editor at our station simply keeping the content fresh. I felt like if I could reclaim some of that time, I could spend more hours on Information Architecture, design, new features...

• ptvGuy

  • So, how much of your site is actually being driven by Movable Type? I mean, I can see from the code that your pages are put together by Dreamweaver, so I guess that what I'm asking is how much of the content that a user sees from page to page is fed there dynamically by Movable Type, and how much are you coding into the pages in the more traditional sense to be included?

• Angela Jordan

  I should say that I USED to use Dreamweaver and its great templating system to edit the site (which, no doubt, lingers in some legacy code--you're probably looking at some JavaScript) but, after I started using Movable Type, I switched to BBEdit. (I'm a Mac person.) It was because it was just easier. I've always written my own code anyway, so the feature-rich environment of Dreamweaver eventually became kind of a clunky hindrance. BBEdit was just cleaner and much easier to use.

  Anyway, Movable Type uses templates as well, and ALL of the pages on our station site (with the exception of our membership form and online store which have to reside in the secure part of the site) exist in templates in Movable Type. Movable Type comes with a variety of HTML templates for basic pages that conventional bloggers might use, but you're not limited to using what they provide. You can write your own templates, creating whatever designs and types of pages that you wish, and then the content gets plugged into the pages by using Movable Type tags. They're not dissimilar to HTML, so it wasn't particularly hard for me to pick them up, and basically are used to indicate to the software what data or content gets pulled into your pages.

  So, when I wanted to create our site in Movable Type, I had to decide what content would need frequent or occasional refreshing. That content became the "entries," and most of the rest of the page--the layout and any evergreen content--got written into the templates.

  So, your short answer is that most of the text in the main content areas of our pages exists in entries that can be edited. The header and footer and other features used on multiple pages also reside in modules (much like includes) that the templates use to write the pages. So, if there's a sitewide change, only one edit is required.

  Also, I should point out that although Movable Type does now have the ability to write pages dynamically, we don't use that feature. We use a more "conventional" implementation where the program rewrites static pages when, for example, new content is added. Use of dynamic pages can cause heavier loads on your server, so you may want to avoid that.

• ptvGuy

  • So, can you tell us more about getting such a system set up initially and what it takes to get content into it and back out of it onto the pages of your site?

• Angela Jordan

  I actually installed Movable Type onto our server myself, which is not a requirement. You can pay Movable Type--I can't remember how much--to do the installation for you, but, of course, it saves a little bit if you can do it yourself. I might have been more daunted if I hadn't done it before for my own site, but, after having done it a few times now, I think it's fairly straightforward.

  One problem for us is that our site resides on an Indiana University server, and they don't exactly provide the same level of support that say, a good commercial hosting company might. You have to have one of several databases--we use MySQL--and the support for the MySQL accounts at Indiana University is something like one person for the entire campus, so practically nil. So I pretty much had to figure that out on my own. Again, ultimately not a big deal, but when you don't know what you're getting into it can be frustrating.

  Undoubtedly, the most time-consuming aspect of converting a site from hard-coded pages into Movable Type is working out a meaningful scheme for understanding and organizing the types of content you have on your site. The great thing, though, is that if you spend the time working on that at the beginning, it will pay off for you once you're using the system. No doubt, there will be some tweaks to make after implementation--there certainly were for ours--but that's to be expected.

  Our site is made up of eight separate "blogs," but I refer to them as "content areas." They're divided by topic into "Site Files," "Community Calendar," "News," "Program Promotion," "Station Promotion," "Membership and Development," "Families and Education," and "The Weekly Special" which is a program site for one of our shows.

  Using this system, once it's in place, is pretty simple. A user logs in to whatever content area they want to add or edit material for, creates an entry, saves it, and rebuilds the relevant pages, and the new content is pushed out to our site. You can also schedule publication for the future, so, say you have an entire month's worth of program promotions you want to enter at one time, you can just schedule publication for whatever days and times you want to refresh your content.

• ptvGuy

  • So, are there any surprises we should know about or any rough points where you just had to do some serious code juggling for a workaround?

• Angela Jordan

  For the most part, no. For people who are using Movable Type as a Content Management System though (as opposed to conventional bloggers) and creating their own templates and adding the Movable Type tags to them, you do have to have a pretty good understanding of the way the system works. It takes a little study to acquire a vocabulary of tags so that you can easily know what tags you will need to use to get a particular bit of content onto your page.

  I have used a lot of plugins throughout the system too, and you do have to do some poking around to see what plugins will be appropriate for what you want to do. Plugins are a great aspect of Movable Type. They're little programs that add to or extend the way Movable Type can manipulate your data, and they're all developed by the Movable Type user community and made available, almost always for free, at the Movable Type Plugins Directory. Usually, if there's something you think of that you want to do on your site, someone will have created a plugin for it.

  For anyone who's curious, I have used "ArchiveAnyway," "Compare," "ExcludeCategories," "FilterCategories," "Glue," "MT KeyValues," "MultiBlog," "SmartBody," "SmartyPants," "SomeDays," and "Textile."

• ptvGuy

  • You know, perhaps I'm missing it, but I'm rather surprised to see that your site doesn't make more use of RSS feeds of your content. I mean, with Movable Type in place, you ought to be able to feed out your headlines and program highlights pretty easily.

• Angela Jordan

  I'm glad you asked about that. RSS is built into Movable Type, so it's easy to implement. When I first built the site in Movable Type, RSS hadn't made it to the public broadcasting community yet, and, I have to admit, I wasn't exactly an early adopter myself, so I didn't build it into our site. But we're going to be adding RSS for our news stories, and video podcasts of our news broadcasts and weekly magazine program.

  Of course, by now RSS and podcasts have made their way onto the PBS and NPR home pages, so more and more users are becoming familiar with what they are. I'm sure the demand will grow.

• ptvGuy

  • You know, just a side question now that I'm thinking about it, did you ever consider any of the other blogging engines like WordPress to run your site?

• Angela Jordan

  I didn't, just because I hadn't used them, though I've certainly read good things about WordPress and TextPattern in particular. But, honestly, because Movable Type has been around longer, I think the user community can't be beat. The developer community is constantly creating plugins and thinking up new ways to use the software.

• ptvGuy

  • So, what level of coding or web design ability would you say is necessary to implement Movable Type initially and then to maintain it once it's in place?

• Angela Jordan

  That depends on just what you want to do with it, though I will say it's not a project for beginners! To do what I did, in addition to having a good understanding of HTML coding, you would want to have a basic ability to work with files on your server and the ability to set up the database you need (or someone who can do that for you.)

  It definitely would help to have an inkling of Perl, but that's not required. You don't have to write any code. I had one class in Perl which I didn't finish, and that is the entire extent of my Perl coding knowledge.

  Really, you just need to be comfortable working with computers because you can find directions for almost anything you need to do. And if you pay for installation, then you need to do even less. However, if you're a Perl coder and you want to play around you can get involved with the Movable Type developer community and write your own plugins. You could even end up creating something that's useful to many users in the Movable Type community.

• ptvGuy

  • So, is Movable Type an option that you'd recommend to other stations?

• Angela Jordan

  Yes, though it's definitely not for everyone. If you have the time to devote to the implementation, and if you have the skills to do the coding, and you have the desire to take some of the maintenance load off your shoulders, then I would definitely look into it.

• ptvGuy

  • Well, is there anything else that we should know about Movable Type or anything else that you'd like to share with us before we close here?

• Angela Jordan

  One thing we haven't talked about is the ability of a Content Management System to allow multiple users to add and edit content, and thus relocate some of the responsibility for creating and maintaining content onto other staff at your station, which is exactly what we did.

  Ultimately, part of the impetus for doing this was that I had a baby and took a three-month maternity leave, and having Movable Type in place before I left enabled station staff to keep site content up to date without having to hire someone to fill in for me while I was gone. This is not to say that things went entirely smoothly in my absence, and I did have a bit of damage control to do when I returned, but it did work. And, after I returned to work full time, the staff who'd become, in effect, web editors, continued on in that capacity, and I worked on other projects and other aspects of the site including the current layout and design. As it turned out, I eventually left my job as a full-time employee and am now working part-time from home, still the only web staffer at the station, which I think is both good and bad. But that's been possible partially because of Movable Type.

  If you're the sole web production staff at your station, it's great to unburden yourself of some of your content management duties, but there are tradeoffs. It was hard for me, as a former Ph.D. candidate in English, to surrender a good deal of editorial control over the site that I so meticulously maintained for several years. It's also the case that the staff who have to take over those duties might not necessarily be happy to have more work added to their doubtless already overbusy workdays. Transitions in employees might be good times to try to build these kinds of responsibilities in if you have the chance. And, while Movable Type is designed to be used by the average person, you can't predict what people's comfort level will be with using the system you've set up.

  I remember reading a nice piece by Jeff Veen called "Why Content Management Fails" which is a pretty good argument against implementing a CMS, and, while I don't think his arguments all apply to tiny non-profits like most small public broadcasting stations, I have had occasion to think of it a few times since making this transition. Anyway, food for thought...

• ptvGuy

  • Well, thank you again, Angela, for your time and sharing your experience with us. I know that I certainly appreciated it, and I'm sure that others will to.

• Angela Jordan

  Well. Thanks. It's been a pleasure. If anyone has questions about more specific details of the process I used to transition the site, the templates I built, the way I structured the entries, the plugins I used, really anything, I guess, I'd be happy to provide more information.

Well, there you have it. I hope that all of you found that as interesting and helpful as I did. If any of you have questions for Angela or want to discuss this in more depth, then I really encourage you to leave your comments and questions here to be passed on to her so that we can all benefit from whatever's learned. But, of course, that's not required. Angela can be reached through the WTIU website by using their contact form and specifying "Web Services" in the "Send to" dropdown menu.

Thank you, all, code well, and good night.

If you enjoyed this post, then make sure you subscribe to the RSS feed!

Related posts

• Time, Money, and Accessibility (0)
• The Underappreciated Resource (4)
• Frontline’s Frontline Video (5)
• Localizing Beyond PBS: An Open Proposal (1)
• Google, PageRank, and the Anal Coder (1)