-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Currently, all requirements are listed on one page:
https://make.wordpress.org/themes/handbook/review/required/
With the exception of requirements from Theme Check, which are listed here:
https://make.wordpress.org/themes/handbook/review/required/theme-check-plugin/
Current presentation
The requirements are divided into the following sections:
- Accessibility
- Code
- Core Functionality and Features
- Child themes
- Readme.txt file
- Presentation vs Functionality
- Importing or Downloading
- Documentation
- Language
- Licensing
- Naming
- Options and Settings
- Plugins
- Screenshot
- Privacy
- Image guidelines
- Selling, credits, and links
- Stylesheets and Scripts
- Templates
-It can be difficult to find the requirement if it is not listed in the section you expect it to be in.
Are there any benefits of sorting them by priority instead of in sections?
Should we separate code quality from license and upselling?
-Right now, it is a mix of what you can't do with code, what you can't do on your own website,
and what you can't do with your account.
Discoverability of the examples
Some requirements have examples.
Users still find it hard to find the example they are looking for.
-
These were moved from a separate page into the requirements
page because very few people could find the examples page. -
The examples only show when you use the example toggle.
We decided to hide the examples because we thought the requirements
page would be to big if the examples were visible at all times.
But this means that the text is hidden from the on-page search.