How to create custom content displays in WordPress

Decide what each item needs before building the display. For a directory, for example, you might need a title, featured image, description, location, category and contact link. Use standard posts or pages when those fields are enough.

If the content is a separate type, such as products, properties or team members, use a custom post type. WordPress recommends registering custom post types in a plugin rather than a theme so the content remains available if the theme changes. Custom taxonomies are useful for grouping and filtering those items.

Add the content and assign consistent categories, tags or custom taxonomy terms. You can use WordPress custom fields for simple extra values, but the Custom Fields panel is hidden in the block editor until you enable it under the editor preferences.

If you are registering a custom post type in code, make sure it is exposed to the block editor and REST API where required. A post type that is registered without the needed editor support may not appear as an option in the Query Loop. If its URLs are wrong after registration, save the permalink settings once to refresh rewrite rules.

Edit the page or template where the list should appear and insert a Query Loop block. Choose a pattern or start blank, then select the post type, number of items, ordering and filters. If the post type and filter controls are missing, select the outer Query Loop block and change Query type from Default to Custom.

Use taxonomy, author, keyword or exclusion filters where they fit. Add Pagination and a No Results message so visitors are not left with an empty area when the query has no matches. Remember that a default loop may inherit the page or archive query instead of using your intended custom selection.

Select the nested Post Template block and choose a list or grid layout. Add the post title, featured image, excerpt, date, author, categories, buttons or layout blocks such as Group, Columns or Row. Every change inside Post Template is repeated for each result.

Check the link settings rather than assuming the item is clickable. Titles and featured images do not automatically link to the post in every Query Loop layout, so enable the title link and the featured image's Link to post option where needed.

For a site-wide archive or single-item display, edit the relevant template in the Site Editor if you use a block theme. With a classic theme, the normal template files for a custom post type are single-{post_type}.php and archive-{post_type}.php. WordPress selects templates through its template hierarchy.

This manual route gives you precise control, but it requires theme editing, PHP and CSS. It also becomes awkward when editors need to change queries, custom-field output, sorting or front-end filters without developer help. Keep custom post type registration in a plugin, not in the theme, to avoid losing the content structure during a redesign.

The native Query Loop is a good choice for a simple posts, pages or custom post type list. For complex custom-field layouts, visual queries, reusable templates, front-end filtering, sorting or pagination, a view builder can reduce the amount of theme code required.

WP Toolset Views is a suitable faster route when you want no-code control over custom data layouts. It provides visual queries, templates and filters for dynamic displays, while still allowing the result to be placed in pages or templates. Treat it as an alternative to building and maintaining those query and display rules manually.