Right, that works well enough on a simple site….
but now span that across 12+ CPTs and you have to micro-manage that across 24 or more different package IDs and a conditional statement for two different featured tiers.
At which point, you’d need to most likely create multiple Archive Item templates to make it manageable and not overtax the system with so many conditional checks per listing. Not to mention having to track that for any package changes.
My thought is that if you can key off of a specific keyword that represents a package tier, that your conditional check can span all CPTs…you can manage at a macro level rather than micro. Even as specific packages may roll in or out of the offering, as long as the tiers utilize the base nomenclature, the logic remains intact.
As it sounds like this doesn’t exist then otherwise, please add this for consideration.
Cheers