Skip to content

Rewrite 'Why llmock' to lead with the problem#13

Merged
jpr5 merged 1 commit intomainfrom
docs/why-llmock-copy
Mar 5, 2026
Merged

Rewrite 'Why llmock' to lead with the problem#13
jpr5 merged 1 commit intomainfrom
docs/why-llmock-copy

Conversation

@jpr5
Copy link
Copy Markdown
Contributor

@jpr5 jpr5 commented Mar 5, 2026

Summary

  • Rewrites the "Why llmock" section title and description on the website
  • Old: "Everything you need to test AI integrations" / multi-process architecture focus
  • New: "Stop paying for flaky tests" / leads with the actual pain point: tests hitting real LLM APIs cost money, time out, and produce non-deterministic results

Feature cards underneath are unchanged.

Tests hitting real LLM APIs cost money, time out, and are flaky.
The old copy focused on multi-process architecture; the new copy
leads with what users actually care about.
@jpr5 jpr5 merged commit 7f3a466 into main Mar 5, 2026
@jpr5 jpr5 deleted the docs/why-llmock-copy branch March 5, 2026 17:22
@jpr5 jpr5 mentioned this pull request Mar 19, 2026
4 tasks
jpr5 added a commit that referenced this pull request Apr 3, 2026
Rewrite 'Why llmock' to lead with the problem
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