I write a lot of Python, so if it had been Python, I would have had the tools to properly install it, no problem.
This is the general problem with distributing "programs" with systems that are really better suited to distributing "libraries" (like gem, npm, and pip). If I am downloading a library, I must be writing code in the language, so it's no problem to expect me to have a reasonable tool chain set up. But if it's just a program that I'm going to run, I shouldn't have to have a language-specific package manager (let alone a rvm/virtualenv-type system) installed and configured.
I put it on hold to complete a side project, aggrenda.com - the Pinterest of calendar events.
Then I got married in May, moved, and was accepted into a local startup accelerator with a StartupWeekend project, spacefinity.com.
I do intend to continue after things slow down again =)
"rc file"s have no defined format, and json is a poorer choice than YAML.
I loathe ruby and still use Jekyll because I never have to touch ruby code to use it. I use it specifically _because it is dead simple_.
You're making stuff up.
That's why I prefer TOML. I wish more projects would pick it up for config. https://github.com/mojombo/toml
Why does that matter in this case?
Wacky. I guess all my YAML configuration files in C++ and Java and .NET aren't a thing.
Bonus points if it's agnostic to markup format.
The 1% of static site generators I've seen are written in scripting languages that require me to install an interpreter and related build tools. Then I'm stuck with their own custom template, markup, and configuration language. And I just don't really care to manage all of that. Even as a highly technical user.
I wrote one myself in the 90s in Perl (and have thankfully lost the source code). They're fun to noodle with if you have the time.
I currently run my site on Pelican (and even patched the WP importer so that it properly preserves WP formatting). It's great but terrible. I still have to keep around a virtualenv. I have to maintain templates that I'll never be able to reuse. It's still not quite good enough. It's a good thing I make my money programming in Python and am familiar with the developer tools.
I'd like something a little more hands-off and with fewer dependencies.
I found the OP's suggestion appealing because it sounds like a solution that wouldn't require me to install some interpreter, a bunch of supporting libraries and tools, write my templates in some custom template language, custom configuration language, scripts, yadda, yadda.
It would be nice to have a system that ran as a unix-y daemon or cron job that just took a single dot-file and did everything for you.
My solution was to make an open-source cms with google docs as the editor. I can manage my site from docblogger.org, use the fantastic google docs editor as my wyswig, and can edit the code to do whatever I want, whenever I want.
Code's at https://bitbucket.org/rattray/acvte/ and the interface is at docblogger.org for anyone interested. Very little activity/use so far, though.
posts/
public/
templates/
Posts without valid YAML front matter are ignored (drafts, for example), and the few options available are on the command line, no config file. I run it with upstart and it watches the posts/ and templates/ directories for changes, rebuilds as needed. Pretty much the simplest still-useful static site generator I could think of. Fits my needs anyway.
I'm ashamed to admit i've been working on something along these lines off and on for a while but have nothing brilliant to show for my efforts. But the basic idea is entirely possible.
This is one of the reasons why I think static site generators are really in their infancy. He describes Pelican as "Jekyll for Python". This highlights what is wrong. You shouldn't have to decide on a tool based on what language it is written in; you shouldn't need to know what language it is written in.
A static site generator should have a very simple folder structure, something like:
draft/
published/
site/
templates/
That's it. You write markdown files in draft/ and move them to published/ when you're done. The generator runs as a daemon and spits out site/ No config files. No `bundle install` nonsense.