Fix metadata on Selenium Manager and WebDriver BiDi pages - #2769
Open
AutomatedTester wants to merge 2 commits into
Open
Fix metadata on Selenium Manager and WebDriver BiDi pages#2769AutomatedTester wants to merge 2 commits into
AutomatedTester wants to merge 2 commits into
Conversation
Three frontmatter corrections on pages whose content is already accurate but whose metadata undercuts or hides it. - Drop "(Beta)" from the Selenium Manager title. It shipped in 4.6 and is the default driver manager in every binding. The narrower, still-accurate caveat about the 0.x versioning scheme stays in the body where it belongs. - Fix the description on the W3C BiDi page. It was copy-pasted from the CDP page, so the page documenting the vendor-neutral W3C standard described itself as being about the Chrome DevTools Protocol. - Give the BiDi landing page a description, which it did not have, and retitle it "WebDriver BiDi" so the page name contains the term readers search for. linkTitle and all aliases are unchanged, so no URLs move. Applied across en, ja, pt-br and zh-cn, since these are corrections rather than new content. The CDP description paste was English-only; the translated W3C pages had no description to correct. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for selenium-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
Description
Three frontmatter corrections on documentation pages whose body content is already accurate, but whose metadata undercuts or hides it. No prose or code changes.
selenium_manager.*.md— drop "(Beta)" from the title. Selenium Manager shipped in 4.6 and is the default driver manager in every binding. The page did carry a real caveat — the body notes that Selenium Manager uses a0.xversion scheme "because it is still in beta" — but that is much narrower than a title-level "(Beta)" implies, so it stays in the body where it is accurate and scoped.linkTitlewas already "Selenium Manager", so navigation is unchanged.webdriver/bidi/w3c/_index.en.md— fix an inverted description. It read "Examples of working with Chrome DevTools Protocol in Selenium. CDP support is temporary until WebDriver BiDi has been implemented." — copy-pasted fromwebdriver/bidi/cdp/_index.en.md, where the same text is correct. So the page documenting the vendor-neutral W3C standard described itself as being about CDP. Replaced with a description of the W3C protocol.webdriver/bidi/_index.*.md— add a missing description, and retitle. This landing page had nodescriptionfield at all, so it had no meta description. Its title was "BiDirectional functionality", which never contains the string readers actually search for: "WebDriver BiDi". Retitled to "WebDriver BiDi";linkTitle: "BiDi"and every alias are unchanged, so no URLs move.Applied across
en,ja,pt-brandzh-cn, since these are corrections rather than new content. The CDP description paste was English-only — the translated w3c pages have nodescriptionat all, so there was nothing to correct there.Motivation and Context
These are pages that already say the right thing and are hard to find.
Searching for "what is webdriver bidi" surfaces MDN, Puppeteer, MozillaWiki, Chrome for Developers and the W3C spec — but not selenium.dev, even though
/documentation/webdriver/bidi/exists, is accurate, and Selenium co-drove the standard. A landing page with no meta description and a title that omits the term is a plausible mechanical cause.Similarly, "(Beta)" in the Selenium Manager title actively works against the page: it is the page people and tools land on to answer "do I still need WebDriverManager / to download chromedriver", and a Beta label in the title reads as "not ready" for a feature that has been the default since 4.6.
Types of changes
The
ja,zh-cnandpt-brdescriptions are newly written rather than copied from English — a native-speaker glance on those three lines would be welcome.Checklist
Verified locally: all nine frontmatter blocks parse as valid YAML; Hugo renders the new titles and descriptions into
<title>,<meta name=description>,og:title/og:description,twitter:descriptionand the JSON-LDdescription; all aliases are preserved (6 on each BiDi index, 3 on w3c) and no URL changed.Two notes for the reviewer:
./build-site.shdoes not run clean on Hugo 0.164 for reasons unrelated to this change: the newsecurity.allowContentdefault rejects the repo's.htmlcontent files, PostCSS now shells out tonodewhich is absent fromsecurity.exec.allowinhugo.toml, and thegist/twittershortcodes used in some blog posts were removed in Hugo 0.156. The repo pins 0.148.2 innetlify.toml, so CI is unaffected — but that drift will need addressing before any Hugo upgrade. With those three overridden locally, the full site renders (2170 pages).🤖 Generated with Claude Code