University of Wisconsin–Madison
UW red background with subtle geometric shapes that alternative between dark and light red.

Submit a Feature Request

The WiscWeb WordPress Service and Strategic Communication’s Digital Strategy Team collaborate on the development and design of the UW Theme and its plugins. Because many requests overlap both WiscWeb and the UW Theme, we use a shared feature request board where you can submit new ideas and upvote requests from others.

Things we’d love your input on

  • New blocks, patterns, or features that would support your content needs.
  • Improvements to existing UW Theme 2.0 features or plugins.
  • Any other ways your WordPress and site editing experience could be better.
  • Accessibility enhancements.

On this page

How to submit a new request

Step 1: Prepare to submit

Go to the Feature Requests board in GitLab and sign in with your
UW–Madison NetID. Do not use a username or email.

Open the feature request board

Step 2: Search for similar issues first

Use the search bar at the top to check if a similar request already exists.

If you find a similar request:

  1. Open the issue.
  2. Click the thumbs up icon (👍) below the description to upvote.
  3. Add a short comment at the bottom of the page with why you need it, your site URL(s), and any barriers.

Step 3: Submit new issue

If there are no similar request, open a new issue:

  1. Click the New item button in the top right.
  2. Add a clear title describing the need or problem.
  3. Complete the description prompts.
  4. Select Create issue to submit.
Screenshot of the GitLab sign-in page with a large red X over the username and password fields, and a red arrow pointing to the “UW–Madison NetID” sign-in button.
Choose the UW–Madison NetID option to sign into GitLab.
Screenshot of a GitLab ‘New issue’ form with an example request titled ‘Add a full-page News pattern for news/article posts,’ including a description and example links.
Sample GitLab feature request for a full-page news pattern.

Issues or questions about using the feature request board?

Contact us

How we review and prioritize

Review process (quarterly)

We review all requests every quarter. During each review we:

  • Evaluate new and active requests
  • Ask follow-up questions if needed
  • Suggest alternatives
  • Provide status updates
  • Move items into planning or backlog
  • May close inactive requests (no activity for 6 months)

Closed requests can be reopened if campus needs change.

Prioritization process

We prioritize requests that show broad campus need, which we gauge through:

  • User impact – how many people would benefit, which we gauge through upvotes, comments, and the use cases people share.
  • Business impact – how the request supports campus goals, service needs, or common workflows.
  • Level of effort – the time and complexity required to design, build, and maintain the request over time.

These signals help us make decisions that support the greatest number of people.