SSW WordPress Backlog

This repository tracks bugs, content changes, maintenance work, and improvement ideas for SSW-owned WordPress sites.

No application source code lives here. Use this repository as the public GitHub Issues backlog for WordPress properties that do not already have a dedicated backlog.

GitHub Project

Use the SSW GitHub Scrum project for sprint planning, estimates, priority, and status:

• https://github.com/orgs/SSWConsulting/projects/93

Issue Templates

Use the issue templates when creating work manually. For screen-recorded issues, use YakShaver and route the item to this backlog.

When triaging an issue:

1. Add the relevant Site: <hostname> label when the affected site is known.
2. Keep one Type: label, for example Type: Bug, Type: Feature, Type: Documentation, Type: DevOps, or Type: Refactor.
3. Remove Needs Refinement once the issue is clear enough to action.

Do not include credentials, WordPress admin secrets, private customer data, or other sensitive information in public issues.

Labels

This repo uses the standard SSW GitHub labels plus:

• YakShaver - Created or routed through YakShaver
• Needs Refinement - Needs review before being worked on
• Site: <hostname> - Identifies the affected WordPress site

SSW staff should keep the site labels aligned with the WordPress properties list on the internal projects page.

Related Rules

• https://www.ssw.com.au/rules/github-issue-templates
• https://www.ssw.com.au/rules/labels-in-github
• https://www.ssw.com.au/rules/scrum-in-github
• https://www.ssw.com.au/rules/github-scrum-workflow
• https://www.ssw.com.au/rules/rules-to-better-wordpress