+=head3 Presentation Model\r
+\r
+This pattern seems to more accurately describe the role of the Maypole model.\r
+Martin Fowler describes I<Presentation Model> in L<Separting presentation logic\r
+from the View|http://www.martinfowler.com/eaaDev/OrganizingPresentations.html>\r
+and L<Presentation\r
+Model|http://www.martinfowler.com/eaaDev/PresentationModel.html>.\r
+\r
+The View sends events (e.g. an HTTP request that triggers an Exported method) to\r
+the Presentation Model. This layer responds by interacting with the underlying\r
+domain model, and stores the results in a bunch of variables, which represent\r
+the new state of the View. The View then queries the Presentation Model to\r
+retrieve these new values. In Maypole, this is the role of the C<vars()> method \r
+on L<Maypole::View::Base>, which transmits the new values to the templates. \r