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.

https://github.com/ocsigen/tyxml

In Reason, doc headers need to be written in ocamldoc syntax.

You can find the specification of the ocamldoc format in the OCaml Manual here

Ideally, we'd extract the most relevant information and describe the syntax in Reason snippets, so it's easy to copy and paste them. Maybe give some pointers on best p

Pesy would be a great utility for detecting and reporting common issues with your project setup.
This Issue is to accumulate common issues that pesy is well positioned to detect and warn about.
We don't have enough requirements gathered to actually implement something like this feature but let's discuss the possibilities.
Basically, any time someone is confused by something with native projects