Particles Toolbox — extension README

What this extension does
- Provides a compact searchable list of particles from your WordPress site's REST API.
- Background service worker fetches pages from the API (avoids popup CORS issues).
- Pagination (load more), keyboard navigation, decoded titles and taxonomy display.

Files included
- manifest.json — extension manifest (v3)
- background.js — service worker that fetches particle pages
- popup.html / popup.css / popup.js — UI assets
- content.js — optional content script (kept from the original)
- icon.png, icon16.png, icon48.png, icon128.png — icons for the store

Chrome Web Store publishing checklist
1. Prepare assets
   - Create 128x128 store icon (icon128.png). Currently the repository uses `icon.png` copied into the sizes. Replace with a properly sized PNG for store listing.
   - Create at least 1 screenshot (800x600 recommended) showing the popup UI. Put them aside for the store listing.
   - Optional: promo image, feature graphic.

2. Update privacy & listing
   - Prepare a short and long description for the store listing.
   - Add a privacy policy URL if your extension accesses user data remotely.

3. Packaging & uploading
   - Zip the particles folder (only the extension root contents). On macOS: `cd tools/chrome-extensions/particles && zip -r ../particles.zip *`
   - Sign in to Chrome Web Store Developer Dashboard and upload the zip.

4. Permissions & review
   - Manifest requests `tabs` and `activeTab` and host permission for your particles API. Ensure you justify these permissions in the store listing if asked.
   - Address any review comments from Chrome Web Store (they may ask for clarifications on data usage).

5. Post-publish
   - After approval, you can update the extension version in manifest.json and push updates via the dashboard.

Local testing
- Load the unpacked extension in chrome://extensions (Developer mode -> Load unpacked -> point to this folder).
- Open the popup and verify the list loads, keyboard navigation works, and items open in new tabs.

Developer notes
- If the REST API requires authentication or special CORS headers, you may need to add authentication flows or proxy routes in the background service worker.
- To expose ACF fields in the WP REST API, use the ACF-to-REST plugin or register the fields in rest responses.

Contact
- Mini on a Big roadtrip — https://minionabigroadtrip.nl
