Adding development sponsorship level

[AutomatedTester]

User description

Thanks for contributing to the Selenium site and documentation! A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines. Avoid large PRs, and help reviewers by making them as simple and short as possible.

Adding a new sponsorship level as has been discussed in the PLC meetings

Description

Added the development level as an extension of the Selenium level.

Motivation and Context

To support the companies that are making sure that there are engineers working on Selenium and making it better for everyone.

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

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

---

Type

enhancement

---

Description

• Introduced a new "Development" sponsorship level on the sponsorship page, including its benefits and criteria.
• Added BrowserStack and Sauce Labs as the initial sponsors under the new Development level, with their logos and URLs updated in the sponsors YAML data file.
• Made text formatting and spacing improvements across the sponsorship page for better readability and consistency.

---

Changes walkthrough

Relevant files

Enhancement

_index.html Addition of Development Sponsorship Level and Text Formatting Updates website_and_docs/content/sponsor/_index.html Introduced a new sponsorship level named "Development". Added benefits for the Development level, including special mentions at Selenium events and weekly retweets of Selenium-related content. Updated text formatting and spacing for consistency across the document. +59/-50  sponsors.yml Adding BrowserStack and Sauce Labs as Developer Sponsors  website_and_docs/data/sponsors.yml Added a new section for developers with two initial sponsors: BrowserStack and Sauce Labs. Included logos and URLs for the new developer sponsors. +12/-0

---

✨ PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-code-review[bot]]

PR Description updated to latest commit (https://github.com/SeleniumHQ/seleniumhq.github.io/commit/9003fc57de101dc1110ba43fed33307912904963)

• [ ] Copy walkthrough table to "Files Changed" Tab <!-- /describe --copy_walkthrough_to_diffview_tab -->

[qodo-code-review[bot]]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the changes are mostly text updates and additions with clear intentions, making it relatively straightforward to review. The addition of a new sponsorship level and the update to the sponsors list are the main points of focus.
🧪 Relevant tests	No
🔍 Possible issues	Text Consistency: Ensure all newly added text follows the same formatting and style as the existing content on the page.
	Sponsorship Level Clarity: The description of the new "Development" sponsorship level should be clear about its benefits and criteria to avoid any confusion.
🔒 Security concerns	No

---

✨ Review tool usage guide:

---

Overview: The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR. When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, require_can_be_split_review, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

[qodo-code-review[bot]]

PR Code Suggestions

Category	Suggestions
Enhancement	Improve accessibility by adding alt attributes to images. Consider adding alt attributes to your images for better accessibility. This helps screen readers describe the images to users who may have visual impairments. website_and_docs/content/sponsor/_index.html [86] -<li>Special mention at Selenium events</li> +<li><img src="path_to_event_image.jpg" alt="Special mention at Selenium event"></li>
	Improve SEO and accessibility with more descriptive link texts. For better SEO and accessibility, consider adding more descriptive link texts instead of generic terms like "here" or "this page". This helps users and search engines understand the context of the link better. website_and_docs/content/sponsor/_index.html [216] -<a href="https://opencollective.com/selenium" target="_blank" rel="noopener noreferrer">Open Collective</a> +<a href="https://opencollective.com/selenium" target="_blank" rel="noopener noreferrer">Visit our Open Collective profile</a>
Maintainability	Use consistent case for headings to enhance readability. To enhance readability and maintain a consistent style, consider using a consistent case for headings. For example, if you're using title case for most headings, ensure all headings follow this style. website_and_docs/content/sponsor/_index.html [47] -<h2 class="alert-heading pb-3">General Benefits</h2> +<h2 class="alert-heading pb-3">General benefits</h2>
	Add more context to sponsor items for better manageability. To ensure the data structure is scalable and maintainable, consider adding a description or startDate field to each sponsor item. This can provide more context about the sponsorship and help manage sponsorships over time. website_and_docs/data/sponsors.yml [5] - logo: "/images/sponsors/browserstack.png" + description: "Leading provider of web and mobile testing solutions" + startDate: "2014-07-30"

---

✨ Improve tool usage guide:

---

Overview: The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR. When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

Enabling\disabling automation When you first install the app, the default mode for the improve tool is: pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] meaning the improve tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically.

Utilizing extra instructions Extra instructions are very important for the improve tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

A note on code suggestions quality While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the custom suggestions :gem: tool With large PRs, best quality will be obtained by using 'improve --extended' mode.

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the improve usage page for a more comprehensive guide on using this tool.

[netlify[bot]]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	b808fae6fe9807c95aa7aa9e13b2dcc6bbb1b5be
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/6634c9d98eacc5000876986d
😎 Deploy Preview	https://deploy-preview-1611--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.