WordPress / WordPress/pattern-directory

Add a notice or flag to patterns that have a minimum WordPress version set

Open
#588 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Component] Theme [Status] Needs Design
Dominant language
PHP
Stars
134
Forks
46
Avg merge
9h 4m
Merged PRs (30d)
19

Description

As of https://github.com/WordPress/pattern-directory/pull/536, patterns can have a wpop_wp_version meta value which indicates the lowest WordPress version supported. For example, this Fullscreen fixed cover pattern uses a block that is not supported in WordPress 6.2, so the value has been set to 6.3.

This works for API requests from another site, as they'll use the version supplied (see #536). But users browsing the directory don't get this information. A banner or some other indicator could be added to let the user know (hacked together proposal, would love a real design/writer 🙂):

Screenshot 2023-07-05 at 5 28 43 PM

Maybe it should only be added this if the wpop_wp_version is a pre-release version?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the version metadata behavior introduced in #536 and inspect the pattern-directory page shown in the issue. Define and implement a user-facing notice for patterns with a wpop_wp_version value, including the expected handling of pre-release versions; done means visitors can see the minimum supported WordPress version.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.