In order for you to know how to navigate using the web framework map, you need to understand how the map is structured.
For starters (as a means to slightly better define what a web framework is), the map has a section that lists the requirements of web frameworks (WebFrameworkRequirements). The rest of the map needs a longer explanation...
Any particular web framework provides particular ways in which users of the framework can accomplish certain tasks (for example, generating a dynamic HTML page). Most of these tasks can be found in many web frameworks. Differently put, web frameworks support particular strategies for specifying certain aspects of a web-based user interface.
Instead of comparing individual frameworks, the route taken here is to ascertain what all the different specification strategies are and to relate them to one another. This approach hopefully provides a bit more objective insight. Anyways, given this basic structure it is easy to go further and list the strategies supported by a particular framework.
User interface programming is often structured according to three aspects of a program, or three different concerns: the model, the view, and the controller. (See the Model_view_controller if you are unfamiliar with these concepts.) However, because this map is done from a specific perspective (described in ReferenceModel), it includes only two of those concerns: concerns pertaining to the view (also called presentation sometimes) and concerns pertaining to the controller.
Taxonomies are often used to show how different specimens relate. This is the approach taken in the web framework map also. One big taxonomy would be a bit convoluted, however. The web framework map is done in terms of two taxonomies of specification strategies, one for each area of concern: the ViewTaxonomy and the ControllerTaxonomy.