I have always had difficulty in using a package/library with the help of documentation only. I always look for an example project/tutorial or a use-case. Since majority of the libraries do not demonstrate their use with an example, how do I get the most of the documentation? Do documentations follow a pattern? Some pointers would be vastly helpful.
With experience, this becomes easier, otherwise the test cases are usually a good place to start. I prefer seeing examples as well before digging into the docs.
Rafael Fragoso
Software Engineer | Full-time Dad | JavaScript Enthusiast | Entrepreneur
Usually you get a good understanding when you read through the source code. READMEs are a good documentation point to get started, but if a project don't have that, you can always take a look at their source code, because a good open source project always have good commenting and in-code documentation.
With that in mind, you can setup a sandbox project to learn it, without affecting your actual project. Just create a folder, setup the lib/framework, and when you feel comfortable with it, you can install it in your actual project and start using it.