Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a proposed roadmap for Bidi adoption and Classic deprecation #2215

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

shs96c
Copy link
Member

@shs96c shs96c commented Mar 11, 2025

User description

Description

Adding a blog post on a proposed roadmap for adopting Bidi and deprecating Classic in Selenium

Motivation and Context

We are receiving queries about our plans, and being able to point to written documentation helps a lot.

Types of changes

  • Change to the site (I have double-checked the Netlify deployment, and my changes look good)
  • Code example added (and I also added the example to all translated languages)
  • Improved translation
  • Added new translation (and I also added a notice to each document missing translation)

Checklist

  • I have read the contributing document.
  • I have used hugo to render the site/docs locally and I am sure it works.

PR Type

Documentation


Description

  • Added a blog post outlining the roadmap for adopting WebDriver Bidi.

  • Detailed the transition plan from WebDriver Classic to Bidi.

  • Explained the benefits and features of WebDriver Bidi.

  • Provided a timeline and steps for the deprecation of WebDriver Classic.


Changes walkthrough 📝

Relevant files
Documentation
bidi-roadmp.md
Added blog post on WebDriver Bidi roadmap                               

website_and_docs/content/blog/2025/bidi-roadmp.md

  • Introduced a blog post detailing the roadmap for adopting WebDriver
    Bidi.
  • Explained the differences between WebDriver Classic and Bidi.
  • Outlined the phased approach for transitioning to Bidi.
  • Highlighted the benefits and new features enabled by Bidi.
  • +63/-0   

    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Copy link

    netlify bot commented Mar 11, 2025

    👷 Deploy request for selenium-dev pending review.

    Visit the deploys page to approve it

    Name Link
    🔨 Latest commit e64ed93

    Copy link
    Contributor

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Filename Typo

    The filename contains a typo: "bidi-roadmp.md" instead of "bidi-roadmap.md", which doesn't match the content of the blog post.

    ---
    Missing Header

    The blog post is missing a proper heading after the frontmatter. The word "Roadmap" appears alone without proper formatting as a heading.

    Roadmap

    Copy link
    Contributor

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    General
    Fix filename typo

    The filename contains a typo: "bidi-roadmp.md" should be "bidi-roadmap.md". This
    could affect URLs and links to the blog post.

    website_and_docs/content/blog/2025/bidi-roadmp.md [1]

    -website_and_docs/content/blog/2025/bidi-roadmp.md
    +website_and_docs/content/blog/2025/bidi-roadmap.md

    [To ensure code accuracy, apply this suggestion manually]

    Suggestion importance[1-10]: 7

    __

    Why: The suggestion correctly identifies a typo in the filename ("roadmp" instead of "roadmap"). This is important to fix as it affects the URL of the blog post and could impact discoverability and linking.

    Medium
    Fix heading structure

    The blog post is missing a proper heading structure. The "Roadmap" heading
    appears to be a duplicate of the title and lacks proper Markdown formatting (it
    should be a level 2 heading with ## prefix).

    website_and_docs/content/blog/2025/bidi-roadmp.md [1-12]

     +---
     +title: "Roadmap for adopting WebDriver Bidi"
     +linkTitle: "Proposed roadmap for adopting WebDriver Bidi and deprecating WebDriver Classic"
     +date: 2025-03-11
     +tags: ["selenium"]
     +categories: []
     +author: Diego Molina [@diemol](https://www.diemol.com)
     +description: >
     +  A roadmap for how and when Selenium will adopt WebDriver Bidi and deprecate WebDriver Classic.
     +---
     +
    -+Roadmap
    ++## Introduction
    • Apply this suggestion
    Suggestion importance[1-10]: 5

    __

    Why: The suggestion correctly identifies that the "Roadmap" heading is redundant with the title and lacks proper Markdown formatting. Changing it to "## Introduction" improves the document structure and readability.

    Low
    • More

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

    Successfully merging this pull request may close these issues.

    1 participant