When comparing Wintersmith vs Metalsmith, the Slant community recommends Wintersmith for most people. In the question“What are the best static site generators?” Wintersmith is ranked 5th while Metalsmith is ranked 17th. The most important reason people chose Wintersmith is:
Wintersmith has an extensive Markdown support. Default, it is rendered by [Marked](https://github.com/chjj/marked). However there are plugins available for [others](https://github.com/jnordberg/wintersmith/wiki/Plugins) (such as [Markdown-it](https://github.com/dwaite/wintersmith-markdown-it)).
Ranked in these QuestionsQuestion Ranking
Templating engine comes with Jade plugin and many third-party plugins.
Pro Very flexible
Wintersmith only has a predefined directory structure, everything else can built any way you want.
Pro Built on node.js
Node.js is a software platform for scalable server-side and networking applications.
Pro Flexible beyond a static site generator
Because metalsmith is at its core focused on transforming directories of files, it can be used for more than just static site generation, and could be used as a build tool, a documentation generator, or any use that requires file transformations.
Pro Designed around plugins
Everything in metalsmith is a plugin, and it is designed to make it easy to write new ones.
Pro Chaining API
Metalsmith uses a chaining API that's consistent and simple to use:
Metalsmith(__dirname) .use(markdown) .use(templates('handlebars')) .build();
Con Thin and disorganized documentation
The documentation for Wintersmith is lacking examples and clear explanations. It's also quite disorganized, making it difficult to find what you're looking for.
Con Small community
The Metalsmith community is still fairly small compared to the more popular options. This results in a lack of learning resources and difficulty finding support from experienced users. However, a slack group has recently been started.
Con Not client enabled API chaining
According to the spec on API chaining, the API request/response need to associate an API object to an corresponding controller/action/uri to be able to validate and handle the request/response and the datasets.
Without that, the consuming client service cannot properly validate or relate the datasets from one to the other. Links have no relational value and the api object creates the relationship between the datasets while maintaining an api/dataset relationship with the corresponding controller/action/uri
As such, the current methodology supported would not be able to be called by the client not supported by the client in a RESTFUL manner