Live data from Hacker News

Poll: What's your favorite static site generator?

news.ycombinator.com

51–60 of 124 posts

Re: Poll: What's your favorite static site generator?

#52
post #4

I like Pelican (for blogs). Python, reST + Jinja. Looks like your list is basically Ruby, Node and PHP, excluding all the Python and other language options.

Yeah, the list is only Ruby, JS and PHP currently but will add more generators from other languages as soon as possible.

Re: Poll: What's your favorite static site generator?

#53
post #12

Coleslaw, ye olde Common Lisp static site generator (with optional dynamic backends, if that's how you roll) http://www.cliki.net/coleslaw

Ha. The optional dynamic backend got taken out during a rewrite in August but it was never very interesting. The new plugin and theme support is much more interesting. ;)

Re: Poll: What's your favorite static site generator?

#55
post #42

Now,i'm a web developer and i'm new to this. why don't anyone write a html page from scratch? what is the real use of site generator? i have worked on wordpress, drupal, and others. Anyone please be helpful to me.

Site generators of this type form a happy medium between the inefficiency of writing HTML from scratch (after all, most boils down to templates filled with content) and the inefficiency of regenerating static content upon every request (as WP and Drupal are prone to do). If there's no dynamic stuff on your site, why pull everything from a database? And if you save time by using templates, why roll your own HTML?

but most of the best static sites so far have a different view.. so, to make a different view, we cant use a template. but i would be interested in leaning these things. i'm on a windows. can suggestion how to install and get started with octopress(seems to be the best)?

Re: Poll: What's your favorite static site generator?

#58
Webby (http://webby.rubyforge.org/)

Branch with ruby 1.9 fixes is at https://github.com/namelessjon/webby

It is not under active development, but is for me feature-complete, stable and incredibly flexible. Advantages are:

- pure ruby (no liquid templates needed)

- each page has its own subdirectory where one can put images, scripts etc; your article becomes a 'package'.

- chained templating filters; you can do erb->markdown->your custom filter with minimal effort.

- mostly implemented by extending rake tasks, no extra api to learn and if you know rake you can continue adding features forever.

Post reply on HN