Repository navigation
docs: sharpen positioning — outcomes, 'why not build your own', honest Playwright framing - #2
Merged
Merged
Conversation
Reframe the top-line messaging to answer "why stay with Selenium instead of switching to Playwright?" — the real competitor. Adopt a single canonical one-liner across the tagline, README subtitle, and Design Philosophy sections, and add an explicit Playwright-idea → Selenium Boot mapping (accessibility-first locators, auto-waiting, web-first assertions, convention over configuration) without hiding raw Selenium. - docusaurus.config.js: new tagline (hero subtitle inherits it) - README.md: subtitle + Design Philosophy "why not Playwright" section - intro.md: Design Philosophy + "Why not just switch to Playwright?" table Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…framing
Acts on reviewer feedback across README and docs intro:
1. Answer "why not build your own framework?" — new Design Philosophy
paragraph (README) and a roll-your-own vs. Selenium Boot comparison
table (intro), positioning Selenium Boot as the maintained version of
the home-grown BaseTest/DriverFactory every team rewrites.
2. Sell outcomes, not APIs — flip both feature lists to outcome-led,
feature-named ("Never write Thread.sleep() again — WaitEngine"), keeping
the API name for credibility and searchability.
3. Compare honestly — replace the combative "why switch from Playwright"
heading with the credible "Already invested in Selenium?" framing;
productivity of Playwright without leaving the Selenium ecosystem.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Match the README/docs outcome-led rewrite so the landing page reads
consistently. Card titles now lead with the outcome ("Tests Survive CSS
Refactors", "Flaky Tests Stop Failing Your Build", "Write Pages, Not
Plumbing") while each description keeps the concrete API name for
credibility and searchability. "Zero Boilerplate" kept as-is (already the
flagship outcome term).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reworks the top-line messaging across the README, docs intro, and homepage in response to reviewer feedback. No code changes — docs/marketing copy only.
What changed
1. Canonical positioning (
e6179af)2. Outcomes + honest comparison (
70e6c2d)BaseTest/DriverFactoryevery team rewrites.Thread.sleep()again —WaitEngine"). API names kept for credibility + searchability.3. Homepage consistency (
this commit)Verification
npm run build(Docusaurus) passes clean after every step.🤖 Generated with Claude Code