Views, as the sites run them

Five of the more complicated views the sites run, rebuilt here out of dummy data: the task list of "contrib" at /tasks, a content overview, the course search of "classes", the chores dashboard of "inventory" and the project grid of "portfolio". Between them they cover what the simpler example does not -- a view over a search index, a link from one display to another, rows rendered inline and separated rather than stacked, a bulk form and an operations dropbutton in a sortable table with columns that drop out on a narrow screen, an exposed form that submits itself, and a responsive grid with no pager under it. Each one is a real view, built in memory from the display options the site runs and never saved, so the markup is what the views render pipeline really produces. Each lists two dummy rows instead of a result set, and the query is built but never sent: applying a filter or a sort no longer changes what is listed, and the widgets are here to be themed rather than used. The pagers are told the query matched more rows than are listed, because a pager with a single page renders nothing, and every link of a view -- between its displays, under its pager, out of its rows -- comes back to this page or lands nowhere.