Except that Stasis has no support for on-the-fly creation of items from your Ruby code, no distinction between filters for content and for layouts, no support for non-filesystem data sources, no dependency tracking, and no metadata per item, among other things.
It may be more simple, but it is nowhere near as powerful.
You can do all of this via controllers. You can execute any Ruby code you want before each template renders.
There is distinction between filters for content and layouts, simply use the layout filename in a before block.
You can execute any Ruby you want. You can use ActiveRecord, Redis, whatever. Load YAML for metadata. None of this stuff needs to be baked in, Ruby already does it.
Comments
Except that Stasis has no support for on-the-fly creation of items from your Ruby code, no distinction between filters for content and for layouts, no support for non-filesystem data sources, no dependency tracking, and no metadata per item, among other things.
It may be more simple, but it is nowhere near as powerful.
You can do all of this via controllers. You can execute any Ruby code you want before each template renders.
There is distinction between filters for content and layouts, simply use the layout filename in a before block.
You can execute any Ruby you want. You can use ActiveRecord, Redis, whatever. Load YAML for metadata. None of this stuff needs to be baked in, Ruby already does it.