Thank you @FlaminFig for looking further.
Yes, the ultimate goal would be to have a UI/nav like the one you provided. The issue I see in applying it to my content is…in a single word…exclusivity In the UI/nav you showed, I am assuming content is exclusive to a single tag (e.g. Support, Resources, Events, and Thoughts). With DecarbToday, a blog post can have multiple tags. So, relative to the UI you showed, a blog post can fall under each of Support, Resources, Events, and Thoughts. The exception to this is my Library content that do not have any tags. Library content is separate from the other content.
I don’t know (yet) how to adapt Sparkle 4’s tagging functionality to my content. I developed my way under Sparkle 3.
However, I am steering away from my redesign issue - unresponsive pages. While you see the current production version with DecarbToday.com, I’ve uploaded the redesigned version under DecarbToday.com/test. This will provide insight into exactly what I was trying to describe with words.
In the end, you are giving me insight that leads me to question the direction of my redesign. Can Sparkle 4’s tagging functionality work for me? And if so, does it eliminate the issue I now face with unresponsive pages? And finally, assuming the unresponsive pages issue is resolved (without employing Sparkle 4’s tagging functionality) and Sparkle 4’s tagging functionality can work for me, what advantages does Sparkle 4’s tagging functionality provide me over what I already have in place? For example, would it allow me to get away from manually managing the multiple indices? Would it allow me to include the Library content so I have one pile of content?
p.s. Thanks for sharing the Tasmania Aware site. I do like its UI and can see how I can use it as a model for DecarbToday.