So far we have talked about collections, and setting up single items, we have gone through creating relations, and nesting items from different collections. However, if we just nest items into items, we would end up with too large html pages. Sometimes we need to use just partial data for a specific item. Example would be author name @ article page. We do not need all Person model fields, just some selected for this case.
In order to simplify workflow, and give some structure for a project to be scalable, we introduced 4 default renders for each item.
VPTL model stands for view, preview, teaser, and liner.
HTML Renders
In the next example we can see the view, preview, teaser, and liner renders for a single item (article) in the Articles collection.
Also visible are 3 renders of another collection, Person in this specific case. Setting up each render and selection of renders used is elaborated in finer details on this link (missing link)
Prototyping information for creating complex models (vptl in the wild).
Theming consistently
Class naming for different renders
Large vs modular code
How VPTL concept solves modeling and upgrade model
Importance of templating for larger scale websites/projects ... (stylebook)
HTML Renders
View
Preview
Teaser
Liner
Index (Dynamic List)
Index Renders