release: 1.0.12 — directory listing assets (icon, banner, screenshots)#29
Merged
Conversation
Populates .wordpress-org/ so the plugin's WordPress.org listing card stops looking visually empty: - icon-128x128.png / icon-256x256.png — solid blue gradient (the WP admin palette already in dashboard.css: #003a5c → #0073aa) with a large white 'ODR' wordmark and a subtle dot grid. No bitmap text artifacts at either size. - banner-772x250.png / banner-1544x500.png — same gradient with a white diagonal accent on the right, a thin green keynote bar, and the headline 'ODR Image Optimizer' over the strapline 'WebP - LCP preloading - critical-path cleanup'. Title font scales until it fits the safe zone so the wordmark never bleeds into the accent. - screenshot-1.png / screenshot-2.png — copies of the existing assets/images/desktop.png and mobile.png. Those are real Lighthouse audit dashboards already shipped with the plugin: 100/97/96/100 desktop, 91/100/96/100 mobile. The Screenshots section captions call out the mobile 91 explicitly so the listing stays internally consistent with the 'results vary by theme, hosting, content' hedge added in 1.0.10. readme.txt and CHANGELOG.md get the matching changelog entries; no plugin code changes. Once tagged, the deploy workflow syncs the .wordpress-org/ folder to SVN's sibling assets/ directory.
The desktop audit (screenshot-1.png) shows a clean 100/97/96/100; the mobile audit captured 91 Performance, which visually contradicts the '100/100 Lighthouse' headline on the listing page. Dropping it leaves the 'results vary by theme, hosting, content' hedge in the Description block as the honest expectation-setter. Also adds .venv/ and .lla-*.json patterns to .gitignore — they live in the repo root during local dev and have no business shipping (or being accidentally swept up by 'git add -A').
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
Populates `.wordpress-org/` so the plugin's directory card stops looking visually empty.
What ships
Hedged screenshot captions
The mobile audit displays 91 Performance, not 100. I'm calling that out explicitly in the readme `== Screenshots ==` section:
This keeps the listing internally consistent with the "results vary by theme, hosting, content" hedge added in 1.0.10.
Out of scope
These are functional, not designed. They look intentional — gradient + accent + typography — but a designer with brand work would produce something better. Drop replacement files into `.wordpress-org/` with the same filenames anytime; the deploy workflow will pick them up.
Deploy plan
After merge:
```bash
git checkout main && git pull
git tag v1.0.12 && git push origin v1.0.12
```
The deploy workflow syncs `.wordpress-org/*.png` into SVN's sibling `assets/` folder (separate from `trunk/`), creates `tags/1.0.12/`, and updates `trunk/` with the readme that now references the screenshots.
Test plan