- 🇬🇧United Kingdom AaronMcHale Edinburgh, Scotland
Let's gets some input on the wording at a usability meeting.
At admin/config/search/pages there is a button whose text is "Re-index site." Shouldn't the button text be something like "Re-index on cron runs"? Or better yet, replace the button with a check box for "Enable re-indexing on cron runs." A button is really the wrong UI element altogether.
Also, this element should not be in a different fieldset from the Indexing throttle, because the indexing throttle setting controls what actually happens when re-indexing is enabled. Placing the element in a separate fieldset below the "X% of the site has been indexed" indicator only adds to the confusion, since it gives the impression that we can immediately progress from X% to 100% by clicking the "Re-index site" button.
Active
11.0 🔥
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Let's gets some input on the wording at a usability meeting.