release: 1.0.11 — Description softening + Features/FAQ name alignment#28
Merged
Conversation
Two listing-copy polish items called out in review of the live 1.0.10 page:
- 'Cleanup Service' in the Features block is renamed to 'Kill Bloat' to
match the FAQ wording and the actual setting key ('kill_bloat' in
class-settings.php). Users were being pointed at a name that doesn't
exist in the settings UI.
- The Description's 'Achieve a deterministic 100/100 Lighthouse score on
mobile' is softened to 'Designed to hit a 100/100 Lighthouse score on
mobile under standard configurations'. The performance table still
carries the same numbers and the existing 'reference test site' hedge,
but the headline no longer reads as a guarantee.
Also drops the internal 1.0.9-merge-mishap postmortem note that was
sitting on the public 1.0.10 changelog entry and Upgrade Notice. The
postmortem stays in CHANGELOG.md ([1.0.10] notes section) where it
belongs as historical context, but end users don't need to read about
our orphan-merge-commit story on the wp-admin update screen.
No plugin code changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Listing-copy polish based on a review of the live 1.0.10 page. Three items addressed; the fourth (banner / icon / screenshots) is not in this PR.
What ships
Not in this PR
Directory listing images (banner / icon / screenshots). The `.wordpress-org/` folder is still empty. I deliberately did not generate placeholder PNGs — pushing auto-generated text-on-a-rectangle images to a public plugin listing looks worse than no image at all, and once they're in SVN they're harder to swap out cleanly.
When you're ready: drop the files into `.wordpress-org/` per the dimensions in `.wordpress-org/README.md`, commit, and trigger the deploy workflow (now that `workflow_dispatch` is fixed it'll sync `.wordpress-org/` → SVN `assets/` without needing a tag bump).
Deploy plan
After merge:
```bash
git checkout main && git pull
git tag v1.0.11 && git push origin v1.0.11
```
Tag push fires `release.yml` + `deploy-to-wp-org.yml`. Listing page should reflect the new copy within ~15 min of the deploy job committing to SVN.
Test plan