A row of article cards can look simple, but the way it is built changes how much work your site creates later.

You can make each card by hand. You can also use a WordPress Query Loop to pull posts automatically. Both approaches are useful. The right choice depends on whether the section is editorially curated or operationally repetitive.

SideQuest Stack started with four handcrafted Field Notes cards. They looked right and linked to the launch articles. The weakness appeared as soon as the site needed to grow: every new post required another homepage edit.

That was a maintenance problem hiding inside a design choice.

What static cards do well

A static card is a group of blocks you control directly. You choose the title, description, label, link, color, and position.

Static cards are useful when:

  • the items should stay in a deliberate order
  • the copy on the homepage differs from the post title or excerpt
  • each card needs a different visual treatment
  • the section contains a small set of permanent destinations
  • an editor wants to feature specific pieces regardless of publication date

For example, a three-card “Start Here” section may be better as static content. Those links might always point to the AI Stack, Method, and Disclosure pages. Automatic sorting would add no value.

The cost is upkeep. Every title, excerpt, and link becomes another value that can drift away from the source article.

What a Query Loop does well

A Query Loop selects content according to rules. You can choose the post type, order, number of results, and filters such as categories or tags. A nested Post Template controls what repeats for each result.

This is useful when:

  • the newest content should appear first
  • every card follows the same structure
  • the section should update after publication
  • the library will keep growing
  • category or tag filters can define the collection

On SideQuest Stack, the Field Notes section asked WordPress for the six newest posts. The repeating card design lived inside the Post Template. Publishing changed the content set, not the homepage structure.

The WordPress Query Loop guide notes that titles and featured images are not linked automatically in every layout. That is one small setting with a large usability effect. Always verify that the elements visitors expect to click actually open the post.

Use the maintenance test

Ask one question: When a new item is added, should this section change without a separate page edit?

If the answer is yes, a Query Loop is probably the stronger foundation.

If the answer is no because each selection requires judgment, static cards may be appropriate.

You can also combine both approaches. A homepage might have three permanent static paths near the top and an automatic latest-posts grid below them. This keeps the deliberate editorial journey while removing repetitive upkeep.

Five settings to verify in a Query Loop

Automatic does not mean maintenance-free. Before publishing a loop, check these settings:

  1. Query type: Use a custom query when the page needs its own post rules.
  2. Post type: Confirm the loop is pulling posts, not pages or another content type.
  3. Order: Choose newest-first, oldest-first, or alphabetical based on the section’s purpose.
  4. Items per page: Show enough choices without making the homepage feel like an archive.
  5. Links: Enable links on the post title, featured image, or a clear read-more control.

Then review the Post Template. A useful article card usually needs a title, short excerpt, and date or category. A featured image can help, but it should not become an empty or inconsistent space when some posts do not have one.

Test the empty and overflow states

A section should still make sense when there are no matching posts. WordPress provides a No Results block for that situation. Add a short message or an alternate path instead of leaving a mysterious blank area.

Also test the grid with real titles. Placeholder titles are often shorter than published headlines. A design that looks balanced with “Sample Post” can become uneven when one title wraps across four lines.

For SideQuest Stack, we checked:

  • newest-first order
  • six-post capacity
  • four real posts displayed correctly
  • card stacking at 390 pixels
  • no horizontal overflow
  • readable title and excerpt spacing

Avoid accidental duplication

When replacing static cards, remove or unpublish the old section after the loop is verified. Otherwise visitors may see the same articles twice.

Duplication can also happen if a homepage template already includes a posts list and the page content adds another. Inspect the live page from top to bottom, not just the section you edited.

Choose based on future behavior

The best block is not the one that is fastest to place today. It is the one that behaves correctly after the tenth article, the next redesign, and the next person who publishes a post.

Use static cards for a small, intentional set of destinations. Use a Query Loop for a growing collection governed by clear rules. Combine them when your homepage needs both editorial direction and automatic freshness.

If your site has already become harder to maintain than expected, read How to Repair a Broken WordPress Homepage Without Starting Over.