Skip to content

thisismyurl/wpshadow

WP Shadow

WP Shadow is a local-first WordPress diagnostics and remediation plugin built to help site owners understand what matters, act safely, and recover with confidence.

This repository is the source for the first public beta.

  • Version: 0.Yddd
  • Status: Public beta
  • Requires WordPress: 6.4+
  • Requires PHP: 8.1+
  • License: GPL v2 or later
  • Last updated: April 5, 2026

What Ships Today

WP Shadow currently exposes:

  • 230 display-ready diagnostics across 11 categories via Diagnostic_Registry::get_diagnostic_definitions().
  • 101 executable treatment classes via Treatment_Registry::get_all().
  • 93 automated treatments and 8 guidance-only treatment entries via Treatment_Metadata::get_counts().
  • dashboard, findings, and WordPress Site Health integration.
  • file-write review, local backup, and recovery workflows.
  • activity logging, KPI tracking, and multisite-aware admin behavior.
  • top-level runtime wrappers and WP-CLI commands for diagnostics, scans, treatments, and readiness export.

The plugin is built around a few non-negotiable ideas:

  • advice instead of pressure
  • accessibility as a product requirement
  • safe-by-default workflows
  • plain-English explanations
  • no required cloud dependency for core functionality

Beta Scope

This beta is focused on the core plugin experience.

Included in the current beta:

  • local diagnostics and findings management
  • remediation workflows with apply, undo, review, and rollback guidance
  • backup and restore safeguards for riskier operations
  • WordPress Site Health and dashboard reporting
  • WP-CLI coverage for common diagnostic and treatment workflows
  • accessibility-first admin copy and lower-stress recovery paths

Not part of the current beta:

  • required registration
  • paid tiers
  • cloud-only features
  • telemetry by default

Quick Start

Site Owners

  1. Install and activate the plugin.
  2. Open the WP Shadow dashboard.
  3. Review findings by category.
  4. Apply safe fixes where appropriate.
  5. Use file review or backup workflows before higher-risk changes.

Contributors

  1. Clone the repository.
  2. Install Composer dependencies.
  3. Read the philosophy and feature inventory before changing behavior or copy.
  4. Run the available tests before opening a pull request.
git clone https://github.com/thisismyurl/wpshadow.git
cd wpshadow
composer install
composer test:smoke
composer test:phpunit

If your environment needs an explicit PHP binary for PHPUnit:

php8.3 ./vendor/bin/phpunit --configuration phpunit.xml.dist

WP-CLI

When WP-CLI is available, WP Shadow registers commands for:

  • wp wpshadow diagnostics list
  • wp wpshadow diagnostics run <diagnostic>
  • wp wpshadow scan run
  • wp wpshadow treatments list
  • wp wpshadow treatments apply <finding>
  • wp wpshadow readiness export

Documentation Map

Start with these documents when evaluating or contributing:

Source Of Truth

Public documentation should treat these as the authoritative count sources:

  • the live inventory returned by Diagnostic_Registry::get_diagnostic_definitions()
  • the treatment counts returned by Treatment_Metadata::get_counts()
  • docs/FEATURES.md

Planning notes, archived reports, and placeholder code should not be used for headline totals.

Accessibility And Privacy

WP Shadow is built for people who use keyboards, screen readers, zoom, reduced motion, simpler language, and lower-stress workflows. The docs should help a busy site owner understand what a finding means, what happens next, and how to recover if something goes wrong.

WP Shadow runs locally. The current beta does not require an account, does not require cloud infrastructure, and should not make unexpected third-party requests.

See docs/ACCESSIBILITY.md, docs/PRIVACY.md, and docs/BUSINESS_MODEL.md.

License

GPL v2 or later.


Support and Contribute

Ways to Support

I'm building these tools because WordPress developers and site owners deserve straightforward, practical solutions. There's no tracking, no ads, and you don't need to pay to use these plugins.

If you find them helpful, here are some genuine ways to support the work:

  • Sponsor if it fits your budget: You can sponsor the project through GitHub Sponsors. Sponsorship helps, but it's always optional.
  • Contribute code or ideas: Opening a pull request, reporting an issue, or testing edge cases is just as valuable as sponsorship. Helping me improve these plugins is a great way to contribute.
  • Share your experience: A review on [my Google My Business profile]([Add your Google Business Profile URL here]) or a follow on WordPress.org, GitHub, or LinkedIn helps others find this work.

Report Issues and Questions

Found a bug? Want to suggest a feature? Just curious how something works?

  • File an issue: Use the Issues tab. Include your WordPress and PHP version, and steps to reproduce.
  • Start a discussion: Use the Discussions tab for questions, ideas, or general conversation about the plugin.

Contributing Code

Code contributions are welcome and genuinely valuable. Here's the workflow:

  1. Fork this repository and clone it locally.
  2. Create a feature branch with a clear name (e.g., feature/improve-safety-check).
  3. Make your changes and test thoroughly on edge cases.
  4. Follow WordPress coding standards — run composer run lint:phpcs before opening a PR.
  5. Open a pull request with a clear description of what changed and why.

I review PRs thoughtfully and appreciate well-tested contributions. Contributing is never required, but it's genuinely helpful.


About This Is My URL

This plugin supports the work I do at This Is My URL, where I help WordPress teams build secure, performant, and maintainable sites.

This plugin is built and maintained by This Is My URL, a WordPress development and technical SEO practice. I'm Christopher Ross, a WordPress developer and technical SEO specialist with 25+ years of experience in software development, training, and digital learning.

My Background

  • 25+ years in software development, technical training, and digital systems design
  • WordPress contributor since 2007 with a strong track record helping organizations build practical, maintainable web systems
  • Technical SEO practitioner helping sites improve performance, security, and search visibility
  • Training specialist focused on practical outcomes and helping teams adopt technology with confidence

I believe in straightforward solutions that work. No hype. No unnecessary complexity.

Ways to Connect

License

GPL-2.0-or-later — see LICENSE or gnu.org/licenses/gpl-2.0.html.

About

WordPress diagnostics and site audits: 230+ automated checks for performance, security, SEO, and accessibility with safe remediation.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Packages

 
 
 

Contributors