I’ve had an on-again-off-again relationship with Dave Winer’s Fargo outliner/publisher. I love outliners, and Fargo is a nice outliner, but I don’t really need a new one. My old one works just fine for general note-taking.
On the other hand, publishing with Fargo is pretty slick, so I fired up an outline and made it available at notes.baty.net.
Why? Good question. Mostly, I wanted a place to write things that may or may not be tweet-worthy, but that I feel like sharing. What I should do is keep that sort of crap to myself but I’m way past the ability to do that. I think we all are.
Fargo works by hooking into Dropbox. It writes my outline to an OPML file and keeps it in Dropbox. Also, if configured to do so, Fargo will automatically create a folder (also in Dropbox) of HTML files that comprise a simple website/blog. All I needed to do is get those HTML files to a server somewhere, which I do via Rsync but it could use Github pages or S3 or whatever.
Here are screenshots of my outline and the accompanying rendered site.
If you don’t need more than a simple timeline of posts, organized by Year/Month/Day, it’s a fine system. It’s a nice way to get a static blog rolling. Another benefit is that the entire thing is available as an OPML file. My only concern is that it seems Fargo hasn’t been high on Dave’s list of priorities lately. I think he still uses if for parts of Scripting.com so with any luck it’ll receive more love moving forward. In the meantime, I found it to be lot simpler to get running than something like Jekyll.