Thanks for the reply. However, I didn’t quite get an answer to my main question about how to display posts in a table layout instead of cards or grids on archive pages.

The first link you shared refers to front-end post submission forms, which isn’t what I’m currently focusing on.

What I’m looking for is a way to display posts on a shop category page or a custom post type archive page in a real HTML table, like this:


<table>
<tr>
<td>Post Title 1</td>
<td>Taxonomy Term 1</td>
<td>Taxonomy Term 2</td>
</tr>
<tr>
<td>Post Title 2</td>
<td>Taxonomy Term 3</td>
<td>Taxonomy Term 4</td>
</tr>
</table>


Each row would represent a post, with its title and associated taxonomy terms or meta fields displayed in separate table cells.

That’s the structure I’m trying to achieve. Any help or guidance would be appreciated!

Hello,
Is there a way to create a post loop displayed in an actual HTML table format, similar to how it’s done on:

PCPartPicker CPU Listings

TechPowerUp CPU Specs

I’d like to display my custom post type (CPT) archive pages in a real <table> layout—not just CSS grid designs that mimic tables—because actual tables are better for SEO, allow for easier product/spec comparisons, and scale more effectively across screen sizes.

Each row should include the post title and relevant meta fields or taxonomy terms, with built-in sorting and filtering functionality.

Also, does the Newspaper Theme support filtering and sorting using WP Grid Builder? Or is there another reliable way to enable sorting and filtering of CPTs based on custom taxonomies and fields?

Hello, were you ever able to integrate WP Grid Builder?

Thank you for the clarification! I understand now that implementing compatibility between components and establishing relationships like the one I mentioned will require custom work.

Before I proceed with submitting a request for custom work, could you provide a rough idea or approach on how to implement the compatibility between components? I’m particularly interested in understanding how to create relationships between posts using a post object. I would appreciate any insights or general steps that could help me get started with this.

Thanks again for your help, and I look forward to your advice!

Best regards

Thank you for the quick response and for clarifying the intention behind the prebuilt PCForge website!

I appreciate that the current setup is just an example, designed with a specific workflow in mind, and understand now why it’s structured this way. I also see the importance of setting up custom post types, taxonomies, and custom fields independently to avoid losing them if I uninstall the prebuilt website.

I do have a few follow-up questions to help ensure I’m moving in the right direction with creating a custom solution:

1. Compatibility Logic: I realize I’ve asked this question twice on the forum, so please feel free to delete the duplicate post here. Since compatibility between components isn’t included by default, are there any specific plugins or approaches you would recommend to implement compatibility filtering? For example, if I wanted to set compatibility rules so that only compatible CPUs and motherboards can be selected together, is there a specific method or workflow within Newspaper Theme that would work best?

2. Form Selector for Category Pages: Is there a way to make the form selector lead to a dedicated category page for each component type—like CPU, Graphics, Storage—where users could apply specific filters for each component category? For instance, after selecting a component, it would take the user to that category page to refine their options and then bring them back to the form to choose the next component. Any guidance on setting up this kind of structured flow would be helpful.

Thank you again for your help and the insights into best practices for building out my own component setup. I’m very excited to implement this and appreciate any further guidance you can provide!

Have a wonderful weekend as well!

Best.

how did you fix it