Character string representing post categories doesn't wrap for small screens

[jeremyboyd]

I have these categories listed in the YAML of one of my posts:

categories: ["social class", "unethical behavior", "driving", "attention", "Bayesian models", "hierarchical models"]

These get rendered as a comma-separate string on the Recent Posts widget in my blog:

https://jeremyboyd.org/#posts

When the screen size is too small (e.g., on mobile), the categories string spills out of the container. Looks like the string isn't responsive to screen size--it doesn't automatically wrap like it should. I've included a screenshot that shows what happens--text spills out the right side of the screen. If you shorten the number of categories in the category string then no spillage occurs and everything renders correctly on small screens.

• Link to your GitHub project: https://github.com/jeremyboyd/personal_website
• Wowchemy Version (from your go.mod): 1.15
• Hugo Version (run hugo version): 0.87.0
• Browser/OS: Safari on macOS & iOS
• Wowchemy Template (e.g. Academic): Academic

[gcushen]

The category system wasn't intended to be used with so many labels per page. Does the tag system not meet your requirements for tagging pages with many labels?

[jeremyboyd]

I like categories over tags because the category labels appear in the posts widget. That way readers can see a list of posts with titles, abstracts, and keywords (categories) all at a glance.

If there's not a way to get categories to wrap, is there a way to get tags to show up in the posts widget?

Love the theme. Really appreciate all of the work you've done!

[github-actions[bot]]

This issue is stale because it has not had any recent activity. The resources of the project maintainers are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the main branch, consider contributing a Pull Request with a fix.

If this is a feature request, and you feel that it is still relevant and valuable, consider contributing a Pull Request for review.

This issue will automatically close soon if no further activity occurs. Thank you for your contributions.