I've been tinkering with the framework, and while the learning curve has been minimal, one challenge I've faced is that the documentation is less verbose. However, this can be supplemented by looking at the implementation and tests to understand how to implement certain features.

For example, when testing routes with paths, my initial approach was to use f-strings to build the URL, but that didn't work. After checking out the Emmett test for auth https://github.com/emmett-framework/emmett/blob/master/tests/test_auth.py#L213, I followed the same approach shown there, which solved the issue.

Would it be a good idea to make the documentation a bit more versbose? Perhaps creating a 'testing-how-to.md' or 'orm-how-to-md' that includes snippets for implementing key features and highlights certain gotchas would be helpful. For instance, in the ORM, it's easy to assume that update and update_record are the same due to muscle memory from other ORMs. A quick reference guide like this could be useful for new developers.