Automattic / Automattic/jetpack
Widget Visibility: add existing block visibility options to the block editor / site editor
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
### Discussed in https://github.com/Automattic/jetpack/discussions/29170
Originally posted by **tnchuntic** February 27, 2023
> Just wanted to ask if there is a plan for conversion of Widget Visibility to Block Visibility? This would be very helpful and useful to have.
>
> I am sure that this will solve a lot of things in the FSE world moving forward.
We currently only offer block visibility options for blocks inside the block-based widget editor. We purposefully restricted those options to the widget editor when we first implemented the block visibility feature (see #17413).
Since widgets are becoming less and less relevant with the advent of block themes and the site editor, it would be nice to bring those block visibility controls to the site editor and block editor.
While the site editor and its templates allow you some control over the different blocks displayed on a specific page, block visibility options would bring an additional level of flexibility and control.
Contributor guide
Research direction
Start by reading the linked discussion and issue #17413, then compare the existing block visibility behavior in the block-based widget editor with the block editor and site editor. Confirm how templates affect the available controls; done means the existing visibility options are available consistently in the requested editors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100