Too Long; Didn't Read
When evaluating a new tool, the developer experience matters as much as the offered features. Getting started guides are typically the first document you read when evaluating a tool. This post aims to help you identify key factors to look for, how that might reflect on the project, and how well it will meet your expectations. A bad experience is likely to put any casual reader off of investigating further. Good documentation is structured to ensure that code is important to ensure it surrounds code examples, so there is more chance you notice it is more annoyance for anyone reading it.