Repository navigation
docs(why): add "Why Selenium Boot / not plain Selenium / not Playwright" pages - #17
Merged
Merged
Conversation
…ht" pages Closes #5 Three top-of-funnel philosophy pages under docs/why/, adapted from the intro Design Philosophy and README: - Why Selenium Boot? — layered philosophy + outcome-led "what you get" table - Why not plain Selenium? — the boilerplate-you-own argument, without hiding Selenium; incremental adoption - Why not Playwright? — honest, does NOT claim to replace Playwright; cross-links to the Coming-from-Playwright bridge page New "Why Selenium Boot" sidebar category placed right after the intro. Pages cross-link to guides and migration pages instead of duplicating content (keeps SEO authority consolidated). SEO description frontmatter on all three. Build passes. 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.
Closes #5
What
Adds three top-of-funnel "Why" pages under
docs-site/docs/why/, adapted from the intro Design Philosophy and README (most material already existed):DriverFactory,WaitUtils, retry analyzer, screenshot listener, reporting glue), the "…without hiding Selenium" escape hatch, and incremental adoption.Notes
Acceptance criteria
description:frontmatter (SEO)sidebars.js)npm run buildpasses (no broken links/anchors)🤖 Generated with Claude Code