What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Pods Framework lets you build structured content in WordPress through the admin interface: create custom content types, add fields, connect related records, then choose how the information appears on your site. The key is to design the content model before you start adding fields. A directory, for example, might need separate People, Organizations, and Locations records, with relationships between them.
Plan your content model before opening Pods
Start by listing the kinds of information your site manages and how those records relate. WordPress already includes posts, pages, categories, and tags. Pods adds an administration interface for creating additional content types and custom fields, so you can represent content that does not fit neatly into those defaults. The Pods documentation explains what Pods is.
For each content type, decide whether it needs its own archive or URL structure, editorial workflow, or permissions. Then note the fields it requires and which other records it should link to. A directory might use People, Organizations, Locations, and Categories; a property site might link each Property to a Neighborhood. These decisions help you avoid creating duplicate information or fields that should instead be relationships.
Create your first Pod
In WordPress administration, go to Pods Admin → Add New. The beginner-oriented build sequence is to create a post type or taxonomy, add fields under Manage Fields, populate the content, and check that the new type appears in the theme. The Pods build guide covers the initial workflow.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
- Choose what to create. Select a custom post type, taxonomy, or another supported content model based on the job it needs to do.
- Name and configure it. Use clear singular and plural labels that editors will recognize, and set the relevant options for how it behaves in WordPress.
- Add fields. Use Manage Fields to define the information editors will enter for each record.
- Save and inspect. Confirm the new type is available in the admin and that its editing screen makes sense before building out the front end.
Choose fields that reflect the data
Pick a field type that matches what the value means, rather than treating every value as plain text. Pods supports common data such as text, numbers, dates, media, repeatable values, and relationships. The WordPress.org Pods listing describes the plugin’s field capabilities.
- Use text for short labels or descriptive content, and number fields for values that should be numeric.
- Use date fields when an editor is entering a date that the site may need to sort or present consistently.
- Use media fields for images or other media attached to a record.
- Use repeatable values when an item can have multiple entries of the same kind, and decide how editors will add, remove, and order them.
- Use relationship fields when the value is another record in your content model, not just text that happens to resemble a name.
Group related fields into logical sections so the editing form remains navigable. Where the form changes according to another field’s value, conditional visibility can keep irrelevant options out of the editor’s way. Test required settings and conditional behavior with realistic records before relying on them in production.
Choose whether to create or extend a content type
A new custom post type is not always the right answer. Pods can also add fields to existing WordPress objects and plugin-created types. Extend an existing post type, page, taxonomy, user, media item, comment, or compatible plugin type when the added data belongs to that object. Create a separate type when the item needs its own archive, URL structure, editorial workflow, or permissions.
Advanced Content Types (ACTs) are another option when a model calls for separate database tables rather than the standard WordPress content storage. They have different capabilities and implications from custom post types and taxonomies; review Pods’ content type comparison documentation before choosing. In particular, compare storage, relationship behavior, how editors will manage records, display and query needs, and compatibility with your theme and plugins. A choice that fits the editor screen may still affect how the site retrieves or migrates the data.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallConnect related records with relationship fields
Use a relationship field when one record should point to another—for example, a Book to its Author, a Property to its Neighborhood, or a Course to its Instructor. This keeps the linked record’s name and other details maintained in one place instead of duplicated as text on every item. Pods documents relationship fields and relationship support in its features overview.
Before creating a relationship, decide its direction and cardinality: can one record link to one other record, several records, or can both sides link to many? For a many-to-many connection, consider how editors will select and maintain links, and how the site will query and display them. A relationship model that is technically possible can still be awkward if the editing workflow is unclear.
Rank #4
Enter sample records before styling the site
Add several representative records before committing to a front-end design. Include a record with optional fields left empty and one with realistic edge cases, such as a long title, multiple related items, or a missing image. This helps reveal whether field labels, required settings, relationships, and the editing form work in practice. Pods’ quick-start build sequence places content population before display prototyping.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose how to display Pods content
The right display method depends on whether you are working in the editor, a page builder, or theme code. Pods supports blocks, shortcodes, widgets, templates, automatic theme integration, and WordPress/PHP retrieval methods. Its display documentation explains available approaches.
Best Value
- For editor-led pages: use Pods Blocks, shortcodes, or widgets where they fit the page-building workflow.
- For theme work: use automatic theme integration or WordPress retrieval methods to incorporate field values into templates.
- For learning field output: the Pods tutorial collection demonstrates adding fields to native posts and displaying values with shortcodes and templates.
Test output with records that have empty fields and different relationship counts. Decide what should happen when a value is missing, and make sure a relationship displays the intended linked information rather than only its stored reference.
Account for the Pods 3.3.1 template change
The WordPress.org changelog records that Pods 3.3.1, released May 2, 2025, removed PHP support for Pod Templates and Pod Pages and points users toward the newer secure theme hierarchy approach. Do not assume older instructions that rely on PHP support for those features describe the current path. Check the Pods changelog and current display documentation when choosing an implementation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
