Skip to content

docs: settings-page screenshots for plugin storefronts - #8

Merged
MyPrototypeWhat merged 1 commit into
mainfrom
docs/screenshots
Oct 26, 2026
Merged

MyPrototypeWhat merged 1 commit into
mainfrom
docs/screenshots

Conversation

@MyPrototypeWhat

Copy link
Copy Markdown
Contributor

What

Two screenshots of the refkit settings page in DeepSeek Harness. Plugin storefronts show them:

  • docs/screenshots/settings-keys.png: the plugin header (icon, name, description) above the API keys section.
  • docs/screenshots/settings-search.png: the search tuning section.

screenshots.json sits next to package.json, which is where dsh-market's detail view and the awesome-dsh-plugin catalog look for it. They read it from this repository's default branch on their next nightly build, so no npm release is needed.

How they were taken

  • Host: an isolated dsh 0.2.1-rc.2. DSH_HOME pointed at a scratch dir, and the plugin was @refkit/dsh-plugin from npm.
  • Capture: headless Chrome at 1280×820 with a 2× device scale (2560×1640 PNG), English UI, light theme.
  • No keys are set, so every key shows "Not set".

Checks

  • package-meta now verifies screenshots.json:
    • it lists 1–8 relative paths that stay inside the repo and point at real PNGs;
    • none of them is in a directory that files publishes.
  • typecheck, lint, test (176) pass.
  • pnpm pack --dry-run includes no screenshot.

dsh-market and the awesome-dsh-plugin catalog show AppStore-style screenshots
read from screenshots.json next to package.json. Two 2560x1640 captures of the
refkit settings page on dsh 0.2.1-rc.2 (API keys; search tuning), kept under
docs/ so they stay out of the npm package. package-meta checks the list.
@MyPrototypeWhat
MyPrototypeWhat merged commit 9cfe5a6 into main Oct 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant