This looks like a very cool project, but how many of these tools do we need and how can we differentiate between them? Just in the Ruby world we now have: Webgen, Webby, Nanoc, Staticmatic, Jekyll, Ace, SassRoku, Hobix, Middleman +++ If we include Python, Node and Perl, there should be plenty more to choose from.
I've used nanoc more than a few times. On seeing this, after first I thought "Why would the community need this??"<p>However...<p>I dig the "controller"-based preprocessing and, especially, that the served pages are then processed through the typical host of rendering engines.<p>This should feel very familiar to anyone who has done any Rails or Sinatra.<p>High marks for obviousness! I may have to try this out!
like it, but can't use it emotionally, probably other german speakers also<p>name reminds to much at the cruelty the stasi has done. <a href="http://en.wikipedia.org/wiki/Stasi" rel="nofollow">http://en.wikipedia.org/wiki/Stasi</a>
Looks really cool. I've been frustrated with Jekyll too.<p>Question: how would you create an index/archive page with links to other posts/pages (if you did want to use it as a blog)?
Cool project. I just starting transitioning my blog from the bloated Wordpress to a static site using nanoc. Any (current or planned) benefits of using Stasis over nanoc or jekyll?
Does Stasis (or any of the other tools in this space) allow you to run a service on your web server that you could post new markdown files to, kicking off a recompile of your static site? I'd like to be able to post a new entry without having to hit the command line, re-render everything and rsnyc changes back up.
I think too few companies are throwing out static websites because they think they need something "dynamic" such as a flashy contact form. If they just used static websites and just put an email address and such by which they could be contacted they could save quite a bit on development time and cost of hosting.
I've never used a static site builder in any language, but I'd be tempted to use this. The only problem I see is that, off the top of my head, I can't think of a use for all these extra features. What sort of use cases do people use these generators for (outside of the blogs some have mentioned)?
Everyone seems to have one of these static site generators these days. Probably a lot of people, myself for instance, who have written their own over the years as well.<p>This one looks like it has some interesting ideas related to pre-processing using the 'controller' idea.
If you're about to overlook this because "it's just another damn static site generator", think again. I almost did, but I was very impressed with Statis! It sure is worth a look.
Gorgeous! I will definitely give it a try when I need to build a static site for the library I'm working on. I like the scrolling effect with the links on the documentation site.