If you think of your website pages like a Mail Merge, pulling fields from your Custom Post Types & Taxonomies and inputting them on the front-end, you will get the idea of how Pods Templates work. Pods Templates are designed to output content on the front-end of your website (or anywhere you want to use them) by running your posts through them in a loop, whether that loop is called from a Shortcode, a Pods Widget or using our Auto Templates.
You can create Pods Templates in two ways:
- In Custom Templates, which is the ‘template’ between the Pods starting and ending shortcode tags. You can use Magic Tags within the Custom Template will be output by the shortcode. You can also access the Custom Template in the Pods Single Item Widget and Pods List Items Widget. Example below:
[pods] anything in here is the Custom Template [/pods]
- In Pods Templates, which are accessed under Pods Admin, Templates. This allows you to create re-usable templates that are stored in the database and can be called specifically in your shortcodes using
template="Name of Template", in the Widgets in the Template drop-down lists, or within the Auto Templates configuration.
You can put anything you’d like in your Pods Templates (HTML5, CSS and jQuery) as long as you recognize that whatever is in that template will be repeated for every item you push into the template, just like a Mail Merge.
More Documentation on this Topic
Using Shortcodes in Pods Templates
In order for Shortcodes to be processed in Pods Templates, you do need to make some changes to your configuration.
Limitations of Magic Tags and Pods Templates
Pods Templates and Magic Tags were never intended to completely replace the power of PHP or WordPress Theme Templates. We discuss many of the limitations in this document and possible alternatives or workarounds.