There are some limitations when using Harold. Hopefully, we solve most of them over time.
Harold doesn't support nesting directories for Pages and Posts. It is something which we will introduce later. It would need some core rewrites, which is quite time-consuming, and the value of that isn't tremendous.
For Pages, you should put .hbs files in the pages directory, and the output will be a .html file in the root of the output directory.
For Posts, you should put .md files in the posts directory, and output will be a .html file in the posts directory in the output directory.
You can change the names of directories using .haroldrc config. See the guides section on how to do this.
There is no a simple possibility to have multiple language blogs. When nesting directories are available, I think it will be more straightforward. The quickest solution would be to host two separate instances in subfolders of the main website. Like for example www.myhost.com/en.
Harold doesn't provide any customization for Scss, PostCSS, and Handlebars. It will be possible to some extent in the future. For now, when it comes to PostCSS, we use only Autoprefixer, and you can define browser support in the package.json file (see how to do this in Autoprefixer docs).
In most cases, the current configuration is good enough.
Harold doesn't support dynamic pagination for posts list at the moment. You can define perPageLimit and currentPage in the postsList helper, but you would have to prepare pagination manually. It is, of course, doable.
It is something for further research for sure.
Harold supports the default set of Markdown tags. Since version 1.3.0, Harold includes a custom markdown processing plugin that enables cleaner syntax for common layouts:
Query Parameter Styling (v1.3.0+):
 - Full-width images - Centered images<iframe src="url?style=embed"> - Responsive embedsThese query parameters automatically wrap elements with appropriate HTML structures, eliminating the need for manual HTML wrappers in most cases.
Traditional HTML still works if you prefer:
<div class="wide-content"><img...></div><div class="embeded-media-container"><iframe...></iframe></div>See the Guides section for more details on query parameter styling.