Skip to content

Clarify term scheduling UI labels and expand README - #5

Merged
torounit merged 6 commits into
mainfrom
fix/ui
Jun 18, 2026
Merged

Clarify term scheduling UI labels and expand README#5
torounit merged 6 commits into
mainfrom
fix/ui

Conversation

@torounit

Copy link
Copy Markdown
Owner

Summary

  • Wrap the scheduling checkbox in its <label> so the whole text is clickable, and rename the field label from "Use scheduling" to "Enable scheduling" so it reads as an action.
  • Reword the checkbox description from "Use automatic term attach / detach." to "Automatically attach or detach this term on schedule.", matching the plugin's existing tagline.
  • Expand the README's Description and Usage sections with concrete examples and step-by-step instructions, and add an FAQ section covering common questions (WP-Cron based execution, empty schedule fields, custom taxonomy support).
  • Add a plugin icon (.wordpress-org/icon.svg).

Test plan

  • composer lint passes
  • Manually reviewed the rendered checkbox/label markup in includes/Term_UI.php

torounit added 6 commits June 19, 2026 07:18
Rename the "Use scheduling" column/field label to "Enable
scheduling" so it reads as an action for the checkbox that turns
on automatic term attach/detach, consistent with how this label
is also used as the checkbox's <label> text.
Replace the terse "Use automatic term attach / detach." with wording
that matches the plugin's own tagline ("Automatically set and unset
the term when the time is up.") and explains what checking the box
actually does.
Explain what scheduling terms is for, how the attach/detach panel and
WP-Cron based scheduling work, and answer a few likely questions
(does it require reopening the post, what empty fields mean, custom
taxonomy support).
@torounit
torounit merged commit f1a9d1e into main Jun 18, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant