It's getting to be about time we split Taylor into separate ORM and view/blueprint libraries.
We can probably keep the name 'taylor' for the ORM side, or perhaps rename it to 'tailor' since that's more in line with the intent of it 'stitching' queries together. But that leaves the question of what to call the view side of it?
Do we want start grouping libraries under the praxis "brand"? Call it something like "praxis-display" or "praxis-views" (although we should try to stay away from views, as that might get confused with with actual template rendering)?
For that matter, do we want to rename attributor? As it is, its entirely standalone, is useful without anything else in praxis, and is extremely competitive with similar libraries out there already, so we don't really want it to seem like it's too tied to praxis. At the same time, it sure simplifies the naming and branding!