# .wordpress-org/ — WP.org Plugin Directory assets

Files in this folder are **NOT shipped to the user's WordPress install**. On tag-based release, `10up/action-wordpress-plugin-deploy` copies them to `plugins.svn.wordpress.org/printcart-integration/assets/`, which the WP.org plugin page loads at:

- Header banner
- Grid icon
- Screenshots section

They are versioned in git so a change to the icon/banner/screenshot goes through PR review like any other change.

## What to put here

| File name (exact) | Purpose | Required size | Format | Required? |
|---|---|---|---|---|
| `icon-256x256.png` | Grid icon (large) | **256 × 256** | PNG (transparent OK) | Yes |
| `icon-128x128.png` | Grid icon (fallback) | **128 × 128** | PNG | Yes |
| `icon.svg` | Vector icon (preferred over PNG when present) | Any | SVG | Optional |
| `banner-1544x500.png` | Page header, retina | **1544 × 500** | PNG (no transparency) | Yes |
| `banner-772x250.png` | Page header, standard | **772 × 250** | PNG | Yes |
| `screenshot-1.png` | Screenshots section — matches `1.` under `== Screenshots ==` in `readme.txt` | ≤ 1200 × 900 recommended | PNG or JPG | ≥ 1 |
| `screenshot-2.png` | Matches `2.` in readme | Same | Same | Optional |
| `screenshot-N.png` | And so on, in order | Same | Same | Optional |

### Filename rules WP.org enforces

- `screenshot-<n>.<ext>` — numeric, matches order in `readme.txt`
- No spaces, no uppercase (matching `screenshot-1.png`, not `Screenshot-1.png`)
- Extension: `.png`, `.jpg`, `.jpeg`, `.gif` — pick one, be consistent per shot
- SVG icon takes precedence over PNG on retina displays

## Current status

The plugin was published to wp.org **before** this asset flow was set up, so the live listing may still be using assets uploaded by hand via the old SVN process. On the next release you can either:

- **Keep the current live assets** — leave this folder empty. `10up/action` will only overwrite what it can find here.
- **Refresh the assets** — drop the exact filenames from the table above into this folder. On the next tag push, they will replace whatever is currently on SVN.

## Testing before release

Run the `Dry-run WP.org build` workflow (Actions → Dry-run WP.org build → Run workflow). It only builds the trunk payload — it does NOT touch this folder or SVN. Assets are picked up only by the real `Deploy to WordPress.org` workflow on a version-tag push.

## Reference

- Guidelines: https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/
- Filename rules: https://developer.wordpress.org/plugins/wordpress-org/plugin-headers/
- 10up action docs: https://github.com/10up/action-wordpress-plugin-deploy#assets
