This post is a continuation of this one. It discusses how to output a generic content page that loops through all properties of that page and outputs them automatically. So, for document types that are quite similar, only 1 template is required instead of 1 for each. Also, I’ve been looking at the zurb foundation reveal component, specifically using ajax to load content into it.
This post is extending the one about the angular property editor. I’ve developed the property editor and functionality to create a content lister that shows child pages on the front end using MVC webgrids and allows the user to configure which properties are sortable, filterable etc.