If you don’t get it, run on over to Google Image Search and look for “terrorist training camp”.
Are you attending Google I/O? I’m not, but @davidangry is.
Submit your best @davidangry Google I/O story on Twitter. After the conference ends, the best Tweet wins a $20 Amazon gift certificate.
- Your tweet must mention @davidangry (so I know how to find it)
- Your tweet must include the #io2009 hash tag
- I am the judge.
The contest is real. @davidangry is not. Let the tweeting begin.
Head over to Twittch to leave comments.
Head on over to Twittch.com for tonight’s new comic.
Comic 4 is up, go to Twittch to see it.
As requested, the Twittch Atom feed now includes full-size comics.
On a technical note, I publish Twittch using Yummy FTP. Yummy is super fast and easy, but still requires “going into an FTP program” to publish. Via Daring Fireball, I found ExpanDrive a few hours ago.
ExpanDrive looks exactly like what I really need: it treats your FTP site just like a USB drive. If all goes well, I should be able to create a shell script with rsync to publish changed files to my web site, in conjunction with ExpanDrive.
I posted a new comic over on Twittch a little while ago:
For each new comic, I do the following:
- Create a new, numbered directory on my filesystem.
- Create an SVG file using Inkscape.
- Export three images: the full-size comic, a 320-pixel wide mobile version, and a 320-pixel wide teaser comic for the Atom feed and the image shown above.
- Create a .properties file with the comic title, tooltip, tags, characters, and publication date.
- Run a program that generates the site on my hard drive.
- Using Yummy FTP, I synchronize the site to my ISP.
I commit the SVG, PNG, and .properties files to git. I do not commit generated files to git.
Although the Atom feed appears in the “normal spot” in any modern web browser, a few people missed it. So I put a feed icon directly on the page to alleviate this problem.
I use Google Friend Connect for comments. I just added it a few hours ago, and am looking forward to seeing what kinds of gadgets Google comes up with next.
So why write a static publishing tool?
- I don’t want to deal with WordPress upgrades.
- I want 100% control over every single URL.
- I want the most scalable possible site in case I’m ever on Digg.
- I can (and do) store all content in git with full history.
- Because I wanted to.
You’ll have to stay tuned. But I do plan to publish at least weekly, and a mobile version of the site is high on my priorities list.