WordPress / WordPress/performance
View Transitions: Provide a clean mechanism for disabling the Settings UI
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 461
- Forks
- 165
- Avg merge
- 11h 12m
- Merged PRs (30d)
- 28
Description
Feature Description
I'm loving View Transitions and am strongly considering using it in our multisite environment ahead of its hopeful adoption by Core. In our environment, Site Administrators lack knowledge of what just about any of these settings do, and I'd hate to present them to our users both because they could easily break them - but also they're just clutter/confusing.
Instead, we would use a pre_option_* filter to enforce our preferred settings.
We could surely hack up some settings removal with javascript, or hide with CSS, but I'm hoping you could include a basic filter or flag on whether or not to display the settings.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the View Transitions settings UI and reviewing how its options are registered and rendered. Compare the available approaches with the requested pre_option_* enforcement, then define a filter or flag that lets site administrators hide the settings while preserving configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100