Skip to content

docs: lead the README with what ZYNLEX is and who it's for - #23

Merged
webtools-dotcom merged 1 commit into
mainfrom
docs/search-positioning
Sep 27, 2026
Merged

webtools-dotcom merged 1 commit into
mainfrom
docs/search-positioning

Conversation

@webtools-dotcom

Copy link
Copy Markdown
Owner

Why

Google and AI search answers were describing ZYNLEX from SECURITY.md rather than the README, and framing it as an "HTTP manipulation proxy" / Burp-style security tool. SECURITY.md's opening paragraph was the densest plain-prose description of the project anywhere in the repo, and it was a list of attack surface. The README opened with a logo, badges and a GIF, with almost no text to summarise.

Changes

  • README: plain-text intro under the tagline stating what it is and for whom; mock responses moved up the feature list; new "Who it's for" and "How it compares" (DevTools, Charles/Proxyman, Postman, Polypane) sections; installer size corrected to 3.6 MB.
  • SECURITY.md: opens with what the policy covers and links the README; same scope and reporting process, mock responses added to scope.

Docs only.

Search engines and AI summaries were describing ZYNLEX from SECURITY.md,
whose opening listed traffic interception, header injection and HttpOnly
cookie editing, so it read as a proxy or security-testing tool.

- README: plain-text intro under the tagline, mock responses near the
  top of the feature list, "Who it's for" and "How it compares"
  sections, installer size corrected to 3.6 MB.
- SECURITY.md: open with what the policy covers and link the README,
  instead of a list of attack surface.
@webtools-dotcom
webtools-dotcom merged commit 2c44f84 into main Sep 27, 2026
2 checks 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