document legacy API
The following discussion from !1 (merged) should be addressed:
-
@sendler started a discussion: I think we should include documentation according to the specifications in the TR, for anything, even legacy code. Should this become any sort of flagship project, documentation shouldn't be as patchy as it is in other projects.