Skip to content

selenium.dev modernisation: tracking issue and review order #2912

Open

Description

@AutomatedTester

This issue tracks the selenium.dev modernisation work: a set of small PRs, one per item, that together turn the site into something a newcomer or a coding agent can use in under a minute. Review each PR on its own; this issue shows where it all leads and the order to take them in.

Where we want to be

  • A homepage that says what Selenium does and shows the install command and first script above the fold, with no event banner going stale.
  • Getting started on one page: install, first script, run it as a test, next steps.
  • Docs organised by the reader's problem (a Guides section) on top of the API reference, with a site-wide language picker, search, and an on-page table of contents.
  • Legacy (Selenium 2/3), IE Driver Server and CDP material kept but clearly marked and demoted.
  • A first-class AI agents section: setup per tool, a curated llms.txt/llms-full.txt, and a "wrong vs right" page for the patterns agents keep producing.
  • Selenium IDE removed from the site; its page kept under Legacy for old links.

Review order

Each PR is independent of trunk and can merge on its own, but reviewing in this order means the pages you land on already look the way the next PR expects. Merge dependencies are noted.

1. Remove and tidy first

2. Homepage

3. Getting started and downloads

4. Docs information architecture

5. AI agents

6. Follow-ups once the above are in

  • A4: add "Guides" and "AI agents" to the top navigation
  • B4: screenshots for Getting Started and Grid
  • B5: CI page under Getting Started
  • D2: per-tool agent install snippets
  • Fix stale gh-codeblock line ranges found on existing pages (cookies, file upload, alerts, BiDi network)
  • Translations: each PR lists the ja, pt-br and zh-cn pages that now need updating

Review comments so far

These PRs were briefly combined into four workstream PRs (#2905, #2906, #2907, #2908), now closed. Review comments made there have been addressed on the item branches; the threads are still readable on the closed PRs. Open question from that review: the date Selenium IDE stopped being maintained, for the note on the legacy IDE page.

Notes for reviewers

  • CI builds fetch every code sample from the GitHub API with a shared token, so more than about seven site builds in an hour fail with rate limiting. If a build fails in under 20 seconds, re-run it later rather than looking for a fault in the PR.
  • Disclosure: the drafts were prepared with Claude (Anthropic); the author reviewed and edited all content, per the project's AI-assisted contributions policy.

Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions