News updates, tips on using Perch and running a great web design business
In this post, part of our perch_content_custom series I take a look at the sort, sort-order and sort-type options for ordering data returned from Perch.
This post explains the options array used to pass values in the perch_content_custom, perch_collection and App Custom functions.
If you want to sort, filter and re-use the data you have added to Perch then you need the perch_content_custom function. In the first of a series of posts, I explain the basics.
Perch has always had structured content at the core, and both versions of the product enable intelligent, structured content and the use of content models. While standard Perch ties that content to pages, the Collections feature in Perch Runway enables flexible structured content. I take a look at how Perch Runway enables intelligent use of content in your projects.
How the Collections feature in Perch Runway will help you to represent content to editors that is not tied to pages.
A core value of Perch is that the CMS is based on structured data, and on the user of semantic markup. What does this mean and what benefits does this approach bring to designers and developers using it?
One of the core concepts contained in the development of Perch was the desire to create <em>structured content</em>. At edgeofmyseat.com we had been building large-scale, custom systems with structured content at their core for several years. With Perch we wanted to bring that idea into a smaller scale, easily deployed CMS. We don’t believe that small sites should care about their content any less than a large site.