WDSEN-15 WDS Repository Standards

[elpuas]

Closes

#WDSEN-15

Link to test

N/A

Description

This pull request introduces several important updates to align the project with WebDevStudios' branding and development standards. It updates all references from the previous maintainer to WebDevStudios, adds documentation and configuration files to enforce coding standards, and introduces GitHub workflows for code quality and security checks. Additionally, it adds project governance files and updates translation files to reflect the new ownership.

Branding and Ownership Updates:

• Updated all project references from "Plugin Pal" and "robertdevore" to "WebDevStudios" across README.md, pattern-pal.php, composer.json, documentation links, and translation files. This includes plugin metadata, author information, support/documentation links, and repository URLs. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

Project Governance and Community Standards:

• Added a Contributor Covenant Code of Conduct (.github/CODE_OF_CONDUCT.md) and a CODEOWNERS file to clarify contribution guidelines and maintainers. [1] [2]

Development Standards and Automation:

• Introduced an .editorconfig file to enforce consistent coding styles across editors, following WordPress Coding Standards.
• Added GitHub Actions workflows for code quality (.github/workflows/assertions.yml) and security checks (.github/workflows/security.yml) to automate linting and vulnerability scanning on pull requests. [1] [2]

Documentation Improvements:

• Enhanced the README.md with a Coding Standards section and updated installation instructions and acknowledgments to reflect new ownership. [1] [2]
• Added a comprehensive pull request template (.github/PULL_REQUEST_TEMPLATE.md) to standardize PR submissions and reviews.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

AI Assistance

• 🤖 This project was developed with the help of a LLM/AI such as Cursor, Gemini, etc.

Added to documentation?

• 📜 README.md
• 📓 ClickUp
• 🙅 No documentation needed

Added tests?

• 👍 Yes
• 🙅 No, because they aren't needed
• 🙋 No, because I need help

Testing Instructions

---

Reviewer's Testing Checklist

As a reviewer, please verify that the relevant testing criteria are fulfilled and confirmed before approving this Pull Request.

• Visual Regression Testing: Ensure that existing functionality is not negatively impacted by the changes.
• Cross-Browser Compatibility: Test on major browsers (Chrome, Firefox, Safari) to ensure compatibility.
• Mobile Responsiveness: Confirm that the changes are responsive and functional on various mobile devices.
• Theme Compatibility: Ensure that the changes do not adversely affect the site's theme and styling.
• Linting: Check that the code passes all linting checks (PHPCS, ESLint, SassLint). Check if PR passes code quality check.
• Accessibility Testing: Validate that the changes comply with accessibility standards. Run npm run a11y.
• Security Best Practices: Ensure that the code follows WordPress security best practices. Check if PR passes security check.
• Documentation: Ensure that any new features or changes are appropriately documented in the README.md or Confluence.
• Post-Deployment Tasks: Check if there are any tasks that need to be performed after deployment.

[optional] Additional Reviewer Notes or Considerations?