Introducing The Humble Gourmand
Yes, your feed readers are right, I’m actually making a post on here. Though I have about nine partially-finished articles in the queue, all sorts of things have interfered, but I promise not one, but two posts in the next couple of days!
Since moving to DC after college in Maine, my college friends have become among my best. I sang for a few years with Alison and Lauren, and brought Lauren in to work with me when I was at Grassroots, and now we meet up at least once a month or so over dinner for great wine and great conversation.
Alison has spent her still-young career as a journalist writing for financial publications, covering bonds and government regulations (as I understand it). Apparently, she’s damn good at it, but she has long wanted to be a food writer. One night, as we were discussing such things, she proposed starting a food and wine blog with Lauren, who loves her wine. Her goals were to generate a bit of a portfolio and hopefully attract a little bit of attention to either get a job writing or editing a food column/magazine/whatever.
I put on my “I think about this kind of thing all the time” hat and suggested that rather than launching a food blog (Technorati says there are at least 50,000 of those), that she instead launch a little online magazine. Not only would she be able to write, but she could also develop her abilities as an editor and publisher as well, and the publication schedule could keep her motivated moreso than the often fluid/non-existent publication schedule of a blog (obviously, I speak from experience).
Three days ago, we launched the first issue of The Humble Gourmand, which is a monthly (though it may become bi-weekly) online food magazine for the younger, urban demographic — complete with features, recipes, reviews, a wine column, and a blog. I produced the site front to back, and Alison and Lauren wrote the content, with Alison of course taking on the publisher/editor responsibilities.
Even though it’s only been three days, it’s already been a success in almost every way. We’ve had a few hundred visitors, who average about six pages per visit (even organic google referrals average four pages per visit), and we’ve gotten incredibly positive feedback. Several people have volunteered to write articles for an upcoming issue, which can help expand the geographic base for reviews. Most importantly, Alison has been offered opportunities to write for major publications… about food!
From the perspective of a web designer/developer, there were a few interesting things about this project:
- I did it end to end. Since becoming a strategist at Viget, I haven’t gotten to do as much of the designing and developing as I had in the past, so it was nice to be back in the saddle again. I have to admit, some of my IE6 bug-hunting chops were a bit rusty. Hopefully, it’s easy on the eyes, and not devilishly broken.
- I used Django. I’ve been watching and toying with Django for months now, but hadn’t actually done anything of real substance with it. This is exactly the type of site that Django was made for, and it’s been working out swimmingly. I don’t feel like I have many JV hacks in my code, even though I’m pretty much a newbie, so that speaks volumes for the Django book by Adrian and Jacob (seriously, it’s great to have in hard-copy), as well as the rest of the Django documentation. The CMS, which was a major part of most of my PHP-based projects, took up about 1% of my time on the project. After launch, I realized I hadn’t made an RSS feed for anything. Five minutes later, we were all set. It’s great.
- We used Mingle. For project and task management, we’ve been using Mingle, which is geared toward agile-like processes, and it’s been nice. It was recommended in a Viget context by Clinton, and we gave it a go here. Going forward, we may use it for the actual content parts of the site, which could be a cool way to work toward both publishing and development goals. Best of all, since there are only a few of us, it’s free.
We’ll be doing more with it in the coming issues, and it should be a nice fun side project for a while.
I encourage you to check it out, subscribe to the feed, comment on things you like, send private email about things you don’t like, etc. ;) Suggestions are always welcome.
Congratulations Jackson (and Alison)! It’s a great looking site and that line about 1% of your time being spent on the CMS part of the project is a classic. Being able to spend your time on the parts of the site that are unique to your needs, the design and business strategy as opposed to setting up database connections speaks to the power of these frameworks. I’ve been spending some time with Django and have definitely been impressed, especially when it comes to publishing.
Are you coming to WDN this year, Sparkleby?
Nice work Jackson! That’s a sharp looking site :)
Thanks guys!
We’ll see on WDN — nothing planned yet, largely because I’m (shh) house hunting, and that $800+airfare+hotel really needs to go to the down payment right now. That said, it was my best conference experience last year, and I would definitely love to make it back.
You’d all get to see I’m no better on a snowboard than I was then.
Dude, cool site! Is there any way of getting all the updates via rss? Right now it looks like it’s just the blog. I won’t remember to check back for updates without the rss.
One other thing… why do you have to log-in to comment? Can’t you just use akisment for spam blocking? Having to register to comment is such a high barrier to entry that it prevents user participation.
[…] many, many missteps — be careful, that last one may haunt you for a while. I’ve also been paying attention to food and wine magazines lately, so this definitely caught my […]
Thanks, Justin. Since the publication is serial (there will be “issues”, like A List Apart or a print magazine), we’ll be making posts on the blog with each new issue, so that should generally satiate the need for updates. I’ll also be building an RSS feed that excludes the blog, but that’s not quite as simple in Django’s framework, since it involves a number of different models, so I haven’t done it quite yet.
Future plans for the site require the user to have an account, so that’s largely the story there. Also, we’d prefer to have a community of active regulars rather than a larger number of once-off participants, and consistent identities (aka accounts in this case) promote that ideal. Maybe that will change as we go along, but it seems like our ratio of people who have registered to our total number of unique visitors is quite strong (you’d likely be surprised), so the barrier doesn’t seem to extreme right now. We’ll be watching…
All good thoughts, though. Thanks!