## Issue type - [x] Feature Request - [ ] Bug Report ## Requester info **Name:** Erik Geiger **Email:** erik.geiger@wisc.edu **Website:** https://it.wisc.edu --- ## Feature request details ### What problem does this address? Branding standards maintained by Strategic Communications require that "UW-Madison" and "University of Wisconsin-Madison" use en-dashes rather than hyphens. Non-technical communicators however are not consistent in their ability to add en-dashes to content via alt-codes, etc. This creates work for editors, manually correcting the hyphens. This is a UW‑specific branding requirement that applies broadly across institutional sites using UW‑Theme. Centralizing enforcement in the theme would be more reliable and scalable than expecting each site or editor to handle it manually or via custom plugins/theme functions. ### What is your proposed solution? Provide a theme‑level prerender (or equivalent content) filter that automatically normalizes these specific phrases by converting hyphens to en dashes at render time. This would: - Improve branding consistency across UW‑Theme sites - Reduce ongoing manual editorial effort - Avoid modifying stored content, if implemented as a render‑only transformation Ideally, this behavior would be configurable (e.g., opt‑in via theme settings or a filter hook) so sites can enable it as needed. ### How will this impact you? This would increase conformance with campus wide branding standards and reduce repetitive, tedious labor for editors. ### Priority Choose **one** priority level: - [ ] **High** — This feature would significantly expand what I can do in WordPress or support an important workflow or content need. It would provide strong value to many users. - [x] **Medium** — This would meaningfully improve my workflow or make tasks easier, but I can still accomplish my goals without it. - [ ] **Low** — A helpful enhancement that adds convenience or polish, but isn’t essential to my core work. --- ## Bug report (required if a bug) <details> <summary>Bug report details</summary> ### Description Please write a brief description of the bug, including what you expect to happen and what is currently happening. ### Where did this happen? Please include a link to the page, post, or site URL where this happened. ### Steps to reproduce Please write the steps needed to reproduce the bug. ### Screenshots, screen recording, code snippet If possible, please upload a screenshot or screen recording which demonstrates the bug. ### Browser and device: What browser (Chrome, Firefox, etc) were you using and what device (Mac Laptop, Android phone, etc)? </details>