Create a better programming documentation

[Aaron-Junker]

I know, that there are already issues about that the docs are outdated.

But this docs are more like manuals how to do something and not a kind of API reference. But that is what such a big project needs. I have zero view on how PT works, but I need this to implement Monaco Preview. I mean something like what does this file, this class or this variable. Most of this things are specified in the files itself, but there is't a overview.

An example what I call a good API Documentation: https://microsoft.github.io/monaco-editor/api/index.html

So maybe we should take a month were we skip a release to create documention that is up to date and good to understand.

[crutkas]

#761 would be tracking item. Monaco is designed to be consumed into other items and extended which is why they have some great docs. Our goal is stability and getting the core in a proper state so we can easier add in / debug stuff. I know @dend on his journey to add in #4246 has mentioned this as well and i'm going to be working with him to improve this.

Understanding painful spots also helps us understand where to focus for short term gains would be good to know as well.