discovery-investigation

A Drupal site audit systematically examines content types, field weights, and widget configurations to pinpoint editorial friction and configuration gaps. This skill combines automated config YAML scanning with real-time browser testing to ensure no usability issues are overlooked before scoping remediation work.

Yes, performing this Drupal audit requires Lando MCP for configuration access and Playwright MCP for browser interaction. The GitHub CLI is also needed to deploy the generated findings report, ensuring the entire evidence-backed audit process functions correctly.

The best way to find configuration inconsistencies and JavaScript errors for a proposal is using a multi-wave analysis approach. This skill combines automated config YAML scanning with real-time browser testing to identify root causes of editorial friction and compile prioritized critical findings.

Browser-based testing identifies field-level usability issues by interacting with the Drupal site in real-time to detect JavaScript errors and configuration gaps. This process operates across development environments to pinpoint root causes of editorial friction during widget configuration analysis.

Yes, you can generate a visual HTML dashboard for stakeholder review from a Drupal audit. This skill automatically compiles its findings into a structured report and generates a password-protected visual HTML dashboard to facilitate evidence-backed proposal discussions.