I know what you mean about finding that perfect implementation. Take a look at the post grid that comes with VC. That thing is pretty flexible, and I think that by implementing that both for the post type for display, as well as the filters, that you’d have not only a good implementation but one that follows a standard to some degree.

Incidentally, here’s the only code I could come up with to make this work. It is only OK on my site because my home page block 14’s are all dog post types and don’t need the filters because i am filtering to a specific listing-type taxonomy.

// ---------------------------- FILTER HOME PAGE QUERIES FOR DOG LISTINGS!
function home_dog_queries( $query ) {
  
    if ( $query->is_home() ) {
    	$pt = $query->get( 'post_type' );
	if ( is_array ( $pt ) ) {
		if ( in_array( 'dog', $pt ) && count( $pt ) == 2 ) {
			//echo 'POSTTYPE';
			//print_r( $pt );
			$query->set( 'tax_query', array(
				array(
					'taxonomy' => 'listing-type',
					'field'    => 'slug',
					'terms'    => $pt[1],
				)
			) );
		}
	}
    }
}
add_action( 'pre_get_posts', 'home_dog_queries', 1 );

In the post type, I had to list the CPT and tax value to filter in the CPT field e.g. dog, german-shepherds. Kinda crazy but worked. I originally tried putting the tax value german-shepherd into the taxonomy tag filter value, but apparently your code first checks to see if that filter yields any results somehow before it issues a standard query.

I think it depends on the way a person’s brain works 🙂

As a wordpress developer, I have seen some really crazy routes to accomplishing things when using a custom theme, as I’m sure you have as well.

I could see where a non-developer would think that needing an empty side column to fit the sidebar is obvious. Developers are used to setting a global setting and letting the theme figure out some sensible defaults.

I still recommend adding this info explicitly to your docs.

I figured it out. What I couldn’t find in the documentation is that you have to set the row to be a 2/3 + 1/3 in addition to everything else above. I would recommend including that in the docs near the bit about setting the class to td-ss-row for those of us who did not install the demo content.