I am the creator of Stasis. Compare the sheer length of docs for nanoc (http://nanoc.stoneship.org/docs) to those of Stasis (http://stasis.me), and keep in mind that Stasis can do anything that Nanoc does.
This is not the case, not by far. nanoc is aimed at building complex sites and hence has a lot more features than Stasis. Some examples:
- Items can contain arbitrary metadata in nanoc
- You can trivially build multiple representations of a single item in nanoc (e.g. a PDF/txt/html representation of a single markdown file)
- Dependency tracking in nanoc is fully automatic (no need to specify priorities)
- Nanoc is easily extensible using custom filters, custom deployers, custom helpers and more
Statis and nanoc have a different audience. To me, Stasis seems to be aimed at simpler, smaller sites, while nanoc is aimed at much more featureful sites. It is a good thing to have a lot of documentation (nanoc is frequently cited as a good example of how documentation should be handled).
jaspervdj|13 years ago
- Items can contain arbitrary metadata in nanoc
- You can trivially build multiple representations of a single item in nanoc (e.g. a PDF/txt/html representation of a single markdown file)
- Dependency tracking in nanoc is fully automatic (no need to specify priorities)
- Nanoc is easily extensible using custom filters, custom deployers, custom helpers and more
Statis and nanoc have a different audience. To me, Stasis seems to be aimed at simpler, smaller sites, while nanoc is aimed at much more featureful sites. It is a good thing to have a lot of documentation (nanoc is frequently cited as a good example of how documentation should be handled).