selenium.dev modernisation: tracking issue and review order
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 12/100
- Tipo di issue
- Documentazione
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- hugo
- Ambito
- content, documentation
Direzione di ricerca
This is a tracking issue for a series of separate PRs, so it has no single change to make. Start from the linked items in the review order, such as the homepage hero in _index.en.html or the ai_agents.en.md rename, and pick one whose scope is small and unclaimed. Done means that item's PR merges and its listed translations are updated.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
#2892 A5: Remove Selenium IDE from the site— dropped: the IDE is being released again (diemol), so it stays on the site- #2893 A3: Dated event banner (config-driven, hides itself outside its window)
2. Homepage
- #2894 A1: Rewrite the homepage hero (merge after A5; takes A1's
_index.en.html) - #2895 A2: "Used by" strip and GitHub stars (placeholders until logos are cleared)
3. Getting started and downloads
- #2896 B1+B2: Collapse Getting Started into one page, with the Selenium Manager callout
- #2897 B3: Split the Downloads page into install and archive
4. Docs information architecture
- #2898 C3: Demote Legacy, IE Driver Server and CDP in the sidebar
- #2899 C4: Docs search and on-page table of contents
- #2900 C5: Release notes page in the docs
- #2904 C1: Site-wide language picker (please click through the deploy preview)
- #2911 C2: Task-based Guides section (new; links into pages as they are on
trunk)
5. AI agents
- #2901 D1: Restructure the AI agents page
- #2903 D5: Outdated Selenium patterns page (merge after D1; both rename
ai_agents.en.md→ai_agents/_index.en.md, second one needs a trivial rebase) - #2902 D3: Audit
llms.txtand addllms-full.txt(merge last; it lists pages added by C2, C5 and D5)
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-codeblockline ranges found on existing pages (cookies, file upload, alerts, BiDi network) - Translations: each PR lists the
ja,pt-brandzh-cnpages 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
- Lingua principale
- HTML
- Stelle
- 1.4k
- Fork
- 1.6k
- Merge medio
- 4g 2h
- PR unite (30g)
- 78
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di SeleniumHQ/seleniumhq.github.io
-
[🐛 Bug]: Code File of ruby in locator page should be a standalone working exampleForse già presa @rpallavisharma l’ha presa 3 giorni fa. Apertabug needs-triaging
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
SeleniumHQ/seleniumhq.github.io#2952 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Ensure Documentation of all links mentioned in llm.txt file are complete across all binding, with example codeForse di nuovo libera @githarshil l’ha presa 29 giorni fa e non c’è nessuna pull request aperta. Apertagood first issue help wanted
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
SeleniumHQ/seleniumhq.github.io#2890 · 6 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Dependency DashboardAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 15/100
SeleniumHQ/seleniumhq.github.io#1617 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di SeleniumHQ/seleniumhq.github.io
Issue simili
-
marketing
Difficoltà 1/5 1-3 ore Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
cline/mcp-marketplace#3856 ·
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
bioepic-data/bervo#268 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
Comfy-Org/ComfyUI-Manager#3546 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 2 giorni