Pod Pages
(Since 1.2.0) -- WordPress pages on steroids
Pod Pages are different from WP Pages because they support PHP code and wildcards. Wildcards are useful if you'd like a single Pod Page to be able to handle multiple URLs.
Wildcards? WTF?
Wildcards let you re-use Pod Pages. If you have a bunch of events created using Pods, you could create a Pod Page named events/* that'll handle all URLs beginning with "events/" (unless a more specific Pod Page is found).
So, http://yoursite.com/events/my-event and http://yoursite.com/events/another-event and even http://yoursite.com/events/my/event will all share the same Pod Page.
Concept - List vs. Detail pages
There are two main "types" of pages on the internet. There are pages that contain groupings of items (List pages), and there are pages that primarily display details about a single item (Detail pages).
List pages
To fetch a listing of items, you would use the Pod() class along with findRecords(). The findRecords method is used to display items in a certain order that meet certain criteria. See findRecords for more info.
<?php
// Event columns: "name", "start_date", "end_date", "approved"
$Record = new Pod('event');
// Find 25 approved, upcoming events
$Record->findRecords('start_date ASC', 25, "t.start_date >= NOW() AND t.approved = 1");
// See the "Displaying Pod Items" page for more options
echo $Record->showTemplate('my_event_template');
?>
Detail pages
We can pass a single ID or slug directly into the Pod class. This avoids the need to use findRecords. It's still the developer's responsibility to find the ID or slug to pass in. There is, however, a useful function called pods_url_variable that makes it easy to retrieve a variable from the URL string.
<?php
// Example URL: http://mysite.com/events/my-test-event
$slug = pods_url_variable('last'); // returns "my-test-event"
$Record = new Pod('event', $slug);
echo $Record->showTemplate('my_event_template');
?>
NOTE: If passing in an ID, use the one from the pod's own table (e.g. wp_pod_tbl_event), NOT wp_pod.