Fixlink pal

[pallavigitwork]

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.

fixing broken linkedin link.

Description

fixing broken linkedin link.

Motivation and Context

fixing broken linkedin link.

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

Enhancement, Documentation

---

Description

• Added new blog post for Selenium & Appium Conference 2025.

• Fixed broken LinkedIn author links in four blog posts.

---

Changes walkthrough 📝

	Relevant files
Documentation	selenium-community-live-episode1.md Fix broken author LinkedIn link                                                    website_and_docs/content/blog/2024/selenium-community-live-episode1.md Updated author LinkedIn link to correct profile. +1/-1      selenium-milestone-20yrs-blog.md Fix broken author LinkedIn link                                                    website_and_docs/content/blog/2024/selenium-milestone-20yrs-blog.md Updated author LinkedIn link to correct profile. +1/-1      selenium-community-live-episode2.md Fix broken author LinkedIn link                                                    website_and_docs/content/blog/2025/selenium-community-live-episode2.md Updated author LinkedIn link to correct profile. +1/-1      selenium-community-live-episode4.md Fix broken author LinkedIn link                                                    website_and_docs/content/blog/2025/selenium-community-live-episode4.md Updated author LinkedIn link to correct profile. +1/-1
Enhancement	selenium-appium-conference-2025.md Add Selenium & Appium Conference 2025 blog post                    website_and_docs/content/blog/2025/selenium-appium-conference-2025.md Added new blog post for Selenium & Appium Conference 2025 in Valencia. Included event summary, links, and acknowledgements. +39/-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.

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	2a744c2

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Fix incorrect verb tense The conference date is set in the future (March 2025) but the blog post is written in past tense as if the event already happened. Consider changing the tense to future since the event hasn't occurred yet. website_and_docs/content/blog/2025/selenium-appium-conference-2025.md [13] -Selenium and Appium projects joined hands together for the 2025 annual conference of both, which was held from March 26th - March 28th in Valencia, Spain. +Selenium and Appium projects are joining hands together for the 2025 annual conference of both, which will be held from March 26th - March 28th in Valencia, Spain. [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical inconsistency in the blog post where the event is described in past tense despite being scheduled for the future (2025). This change is important for accuracy and reader understanding.	High
	Fix inconsistent date The blog post date is set to 2025-04-21 (in the future), but the post describes an event in March 2025 as if it already happened. Consider using a more appropriate date for this announcement post. website_and_docs/content/blog/2025/selenium-appium-conference-2025.md [4] -date: 2025-04-21 +date: 2024-04-21 Apply this suggestion Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a temporal inconsistency where the blog post is dated April 2025 (after the event) but describes a March 2025 event as if it already happened. Changing to 2024 would make this an announcement post, which is more appropriate.	Medium
More