classic-theme-loop-template-parts

Classic Theme Loop and Template Parts

Use this when creating or reviewing the content rendering layer of a classic PHP WordPress theme: main loops, content.php style partials, archive cards, single post bodies, page bodies, empty states, and pagination.

This is not a block/FSE template-part skill. Use PHP template files and get_template_part().

When to Use This Skill

• Writing index.php, home.php, archive.php, search.php, single.php, page.php, or 404.php.
• Moving repeated markup into template-parts/content*.php.
• Reviewing a nested WP_Query, featured-post section, related posts section, or custom loop.
• Fixing pagination, no-results output, post classes, content/excerpt choice, or "wrong global post" bugs.

Main Loop Contract

For the main query, use WordPress' loop state. Do not replace it with query_posts().

<?php
get_header();
?>

<main id="main" class="site-main">
	<?php
	if ( have_posts() ) :
		while ( have_posts() ) :
			the_post();

			get_template_part( 'template-parts/content', get_post_type() );
		endwhile;

		the_posts_pagination();
	else :
		get_template_part( 'template-parts/content', 'none' );
	endif;
	?>
</main>

<?php
get_footer();

Rules:

• Call the_post() inside the while ( have_posts() ) loop before template tags that depend on the global post.
• Include a no-results state. template-parts/content-none.php is the standard pattern.
• Keep the loop in template files; move per-post markup into template parts.
• Do not call query_posts() in themes. It mutates the main query and breaks pagination and conditionals.
• Do not manually set global $post unless a core API requires it and you fully restore state afterward.

Template Part Pattern

Use get_template_part() for repeated per-post markup:

get_template_part(
	'template-parts/content',
	get_post_type(),
	array(
		'heading_level' => is_singular() ? 'h1' : 'h2',
	)
);

get_template_part( $slug, $name, $args ) searches for: