zavage-software/search-with-chatgpt-powered-by-openai-extension
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: generate the listing images instead of committing them

Browse Source 
The five PNGs are generated output, like the build ZIP, so they leave
git and docs/amo/screenshots/ is ignored. The README's command produces
them, and with squash merges they never reach develop or main, so the
repository needs no Git LFS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
golem
2026-10-18 23:22:20 -06:00
co-authored by Claude Opus 5.5
parent ac734aa3db
commit 71fa5ddbc8
8 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-10-18-amo-listing-design.md
+5 -2
View File
@@ -1,7 +1,8 @@
# Add-ons listing for 1.3
Status: implemented on `docs/24-amo-listing-add-screenshots-and-a` (#24). The
paste-ready text, captions, and images are in [`docs/amo/`](../../amo/README.md).
paste-ready text and captions are in [`docs/amo/`](../../amo/README.md), along
with the page that renders the images.
## Problem
@@ -46,6 +47,8 @@ use the extension.
upload order, and how to regenerate the images.
- `docs/amo/screenshots.html`: the drawing markup at 1280×800, one image per
`#fragment`, styled by `options/options.css`.
- `docs/amo/screenshots/*.png`: the five rendered images.
- `docs/amo/screenshots/*.png`: the five rendered images. They are generated
and git-ignored rather than committed, so the repository carries no binaries
and needs no Git LFS. The command to produce them is in the README.
`docs/` is excluded from the extension package, so none of this ships to users.