Dioxus Service: Outreach / External Documentation

We should update the Dioxus docs (DioxusLabs/docsite) to mention @wdio/dioxus-service as the preferred mechanism for end-to-end testing of Dioxus desktop apps with WebdriverIO.

Dioxus has no WebDriver / E2E testing documentation today, so this is likely a new section rather than an edit. The service ships an embedded WebDriver server (no external driver on any platform), browser.dioxus.execute(), invoke mocking, log capture, multiremote, and a browser mode — all worth surfacing.

We will also need to add the corresponding WebdriverIO docs: there is no desktop-testing/dioxus page yet (unlike the Tauri service, which already has one). This mirrors the Tauri approach — a docs generator that pulls the service docs from this repo, a landing page, and a sidebar entry — and, like the Tauri work, also adds Dioxus to the create-wdio project-creation wizard.

Tracking

• Dioxus docs — not started: DioxusLabs/docsite
• WDIO docs + create-wdio wizard — in progress: webdriverio/webdriverio#15528. Adds the dioxusDocs.ts generator (pulls the dioxus-service reference docs from this repo), a Dioxus.md landing page + sidebar/3rd-party-services entry, and first-class Dioxus support in the create-wdio wizard (embedded/external driver providers, services/capabilities templates, and the Rust-side setup banner).

Use the Tauri equivalent as a template: #30, plus the Tauri-docs PR tauri-apps/tauri-docs#3922 and the WDIO docs PR webdriverio/webdriverio#15235.

Start with the Tauri equivalent in #30 and review the referenced Dioxus docs and WebdriverIO PRs. For the remaining work, coordinate the new Dioxus section in DioxusLabs/docsite with the existing dioxusDocs.ts generator, Dioxus.md landing page, sidebar entries, and create-wdio changes. Done means Dioxus E2E testing is documented and the cross-project documentation links are complete.