WordPress / WordPress/openverse
When exploring integration to WordPress, enable the ability to filter by license and usage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 380
- Forks
- 290
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 8
Description
Problem
When considering integration into WordPress, it will be important to easily see license and usage details in order to help folks make solid decisions. This is especially true since depending on the license, it'll impact attribution which some folks might not want to include on their site:
I want the freedom to use images as I want and modify these as I need without needing to add any attribution information.
This question evoked a strong negative reaction for me. I don’t know it means that attribution info wouldn’t be removable? Would it be watermarked on the image? Are we talking about metadata. Either way, if you can’t remove attribution from an image visually, I would never use such an image or images from such a resource. The same goes for images you can’t make significant images, the very idea makes me cringe.
Description
This feedback came up as part of the FSE Outreach Program's All Things Media exploration:
I talk about how I wish Openverse is integrated into WordPress. I really like the way that Jetpack add Pexels into WordPress, and how that creates a very simple chooser where I can select Media Library, Google Photos, or Pexels. I think something simple like that would be great for the Openverse. If it was integrated, I hope that we will have full access to Openverse’s image filters, where we can filter by license, or if we don’t know what license we need, filter by usage.
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
The issue does not name any files, tests, or entry points. Start by mapping the existing WordPress integration surface and current license and usage filters, then clarify the expected chooser behavior and supported filter semantics. Done should include an agreed integration scope and verified filtering behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100