Reason

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

As marked in https://github.com/briskml/brisk/blob/master/examples/hacker-news/app/Story.re#L82, we'll need to transform incoming html.

<p> tags are not rendered with proper margin/padding by Cocoa in NSTextView by default, and instead of manually changing document attributes on ObjC bindings side, simply pre-processing html text and replacing paragraphs by newline characters seems more prefe

Similar to OCaml documentation - lets do https://realworldocaml.org/ automatically so that learning Reason is painless.

It would be great to have a couple of example apps, similar to Redux and co. inside an examples folder in the repo.

If for some reason, the initial bootstrapper fails (network failure, bad cache etc), creation of dune files in the project could get interrupted - the dune files that trigger the on-the-fly dune rules generation. We could

1. Check in those bootstrapping dune files in the templates
   or
2. Ensure, before running, dune build if dune files are missing.

Ideally, we do both.