The only way to get comfortable with a library is to code with it. The below examples build on the documentation modestly. Highly visual documentation for a visual library was a good move by Framer Motion. With that perspective, I thought the docs were overall really accessible. I like to keep in mind that no library has perfect documentation. I shouldn’t have to go to a third-party resource to find basic info about props for an API. I did, however, find plenty about the different transitions from (with whom I have no relationship, I’m just calling out a great resource).However, the yoyo property was nowhere to be found in the documentation (at least, I couldn’t find it). For example, one CodeSandbox had a yoyo property in the transition object. Documentation seems to be missing on some of the accepted props.The docs got into some technical aspects of animation performance with recommendations of which animations can be hardware accelerated - I was happily surprised to see this The Worst Parts of the Framer-Motion Docs.I enjoyed the fact that examples and example code had more screen real estate than the textual definitions. In the center were the explanations for the declarative API.This is exactly what a visual learner, like myself, needs. There were copious amounts of examples on the right, plus code sandboxes.The nav tree on the left was easy to search and not overwhelming.In my opinion, and for my very visual learning style, the docs quickly gave me a sense of confidence that I could accomplish basic animations with Framer Motion. A screenshot of the Framer Motion API docs
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |