"Welcome to Jekyll!"
UPDATE: I'm not longer using Jekyll, but static site generation remains my jam.
Why thank you, Jekyll. I certainly feel welcome.
After using both Wordpress and home-rolled solutions, I've decided to switch to Jekyll, a "blog-aware" static site generator. With Nodepaper, I decided to move away from a db-based CMS to one based on flat Markdown files. I agree with the makers of Jekyll that it's backward, and I, too, have lost a lot of content from bad hosts.
So it's on to Jekyll and Github Pages, and I'm enjoying the process so far. The idea that a new theme or theme inspiration is just a fork away is exciting. That a correction or comment can be made by Issue (or even a Pull Request) seems ideal and forward-thinking.
Jekyll is not for everyone; it's for makers.
- Jekyll could use a
jekyll addcommand (or similar) to start a new blog post. Not that it's hard to run
subl `date "+%Y-%m-%d"`-some-title.md, but I prefer not to make choices (like what key to press) when the answers are obvious (See: game design). I'll update if I can learn enough Ruby to submit a pull request.
jekyll serve --watchdoesn't provide a lot of information about formatting errors, which is ironic as it's intended to be used during development. While you don't want a big, fat stack trace every time you save if you save as often as I do, it is inconvenient (if minorly so) to have to restart the server to get the stack traces you do want.
- Maruku is the default Markdown processor. I'm not a Ruby programmer, but I understand RDiscount to be better. It should probably be the default, as it produces far better output based on the kind of Markdown I write.
25th of May, 2013