Redundancy is important. Computers are great at going straight from A to Z, but human brains are terrible at it.
Use levels of explanation. A good explanation starts with the basics and then shows you how to progressively update your mental model to include more details and nuance. A good example is the "5 Levels" series from WIRED magazine: https://youtu.be/opqIa5Jiwuw
When appropriate, explain concepts in terms of other concepts that your target audience is already familiar with. For example: @frontity/connect can be explained in terms of concepts from MobX.
Examples are often better than descriptions. Developers don’t read documentation like a book, they just browse it until they find something that “looks” like it might solve their problem and only then start to read more.
Aim for discoverability rather than completeness. The documentation does not have to list every possible option in the API straight away, but rather introduce them slowly and make sure the the user can find those option in the “reference”. Also see next point.
Separate:
Use consistent grammatical tense and voice:
<insert example><insert example>Technical Writing | Google Developers
Google developer documentation style guide | Google Developers