Better documentation

[zchbndcc9]

It would be very nice if there was some more documentation all of the logger apis that are available for use as well as some beginner friendly examples with explanation.

[MaximeGratens]

Plz up

[philliptaylorpro]

It's not obvious from the README what the actual output of that code is.

Ideally logging is always executed and written to disk even if something afterwards blows up inside the program so you can debug it. Whilst side-effects are bad, you can't undo time spent by the cpu so for this reason I assume all log lines are written to disk immediately?

[ChristopherDavenport]

@philliptaylorpro Which backend are you referring to? In Slf4j backend, that depends on how the base logger is configured. They are immediately submitted to the backend logger. However then that logger controls when the unit is returned back to the algebra.

[kubukoz]

I have some ideas for improving the documentation. The testing/noop/writer loggers, structured logging, self aware logging - each of these could get a section. I can spend some time on this (just a couple sentences each, probably everything can fit on the main page of the microsite).

[yamin-oanda]

Did any of this planned documentation end up getting added?