Skip to content

docs: sharpen README first-screen positioning#10

Merged
cigan1 merged 3 commits into
mainfrom
readme-positioning
Jun 5, 2026
Merged

docs: sharpen README first-screen positioning#10
cigan1 merged 3 commits into
mainfrom
readme-positioning

Conversation

@cigan1

@cigan1 cigan1 commented May 30, 2026

Copy link
Copy Markdown
Contributor

What

Strengthens the top of the README so a stranger can decide whether siftfy fits before scrolling into setup details:

  • Audience line — names who it's for (Python devs filtering forms, signups, comments, moderation queues).
  • At a glance — in/out contract, sync+async, retries, deps, free tier.
  • Good fit / Not a fit — honest scope guidance (hosted API; not for offline/self-trained use).

Why

The OSS-readiness README audit flagged a weak first screen (missing audience + fit guidance). With this change it scores a clean go (21/21 checks). Docs-only — no code or behavior changes.

🤖 Generated with Claude Code

cigan1 and others added 3 commits May 29, 2026 21:16
Add an audience line, an "At a glance" summary, and good-fit/not-a-fit
guidance above the fold so a stranger can decide whether siftfy fits in
seconds. No behavior changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Show the input-to-output payoff before any setup, and demonstrate a real
request-handler integration inline rather than only linking out. Docs-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cigan1 cigan1 merged commit 6133114 into main Jun 5, 2026
6 checks passed
@cigan1 cigan1 deleted the readme-positioning branch June 5, 2026 16:03
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