Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Assemble vs Grav, the Slant community recommends Assemble for most people. In the question“What are the best static site generators?” Assemble is ranked 15th while Grav is ranked 17th.
Specs
Question Ranking
Pros
Pro No dependencies on Ruby, Python... just JavaScript
Pro Built on node.js
Pro Powered by a popular template engine Handlebars
Handlebars is the default template engine for Assemble, but you can add any template any you want.
Pro Highly customizable
Pro Markdown support
Pro Highly extensible
Assemble can be extended with plugins/middleware, helpers and mixins.
Pro Nested layout support
Assemble makes it easy to work with layouts. Layouts are used to "wrap" pages with common page elements, such as a header, footer etc. You can even nest layouts!
Pro Use mainstream build tools Grunt or Gulp
Pro Can be hosted with any provider
Since Grav is built with PHP, it can be hosted on almost all web hosting providers. If the provider supports Wordpress, they also support Grav.
Pro Easy creation of templates and content
Supports Twig for templating with Parsedown for fast Markdown and Markdown Extra support.
Pro Easy to use admin panel
Well designed, easily usable and modern admin panel is a boost as it lets Clients edit the content easily.
Pro Custom fields for content
YAML-based page headers allow you easily add custom dynamic fields to your content.
Pro Open-source and free
Pro Extensive Documentation
Documentation is not an afterthought! Grav has a dedicated documentation site plus loads of tutorials and guides.
Pro Extensive documentation
Documentation is not an afterthought. Grav has a dedicated documentation site plus loads of tutorials and guides.
Pro Built-in package manager
Pro CLI Tools
Command line tools such as dependency installation, cache clearing, user creation, and backups.
Cons
Con Documentation can be hard to navigate
Especially for someone new to Assemble, it can be difficult to find what you're looking for in the documentation.
