Coder Laravel Package

Product Decisions This Supports

• Enforce Drupal Coding Standards: Automatically align custom modules/themes with Drupal’s official coding guidelines, reducing technical debt and improving maintainability.
• Developer Onboarding: Standardize code quality checks for new team members, accelerating ramp-up time by eliminating ambiguity in coding conventions.
• CI/CD Integration: Embed into pipelines to block non-compliant code merges, ensuring consistent quality across releases (e.g., GitHub Actions, GitLab CI).
• Build vs. Buy: Avoid reinventing custom linting rules; leverage pre-built, community-vetted standards (Drupal/DrupalPractice) instead of maintaining proprietary tools.
• Roadmap Prioritization: Justify investment in developer tooling by quantifying time saved on manual reviews (e.g., "Coder reduces review cycles by 30%").
• Security/Compliance: Align with Drupal’s security best practices (e.g., deprecated function checks) to mitigate vulnerabilities early.
• Editor/IDE Integration: Reduce context-switching by integrating with tools like PhpStorm/VSCode for real-time feedback (e.g., "Fix on save" for coding standard violations).

When to Consider This Package

• Avoid if:
  • Your team uses non-Drupal PHP projects (e.g., Laravel, Symfony) where Drupal-specific rules (e.g., hook_* naming) are irrelevant.
  • You need JavaScript/TypeScript linting (use ESLint/Drupal ESLint instead).
  • Your project requires custom linting rules beyond Drupal’s scope (e.g., proprietary frameworks).
  • You’re already using a mature alternative (e.g., PHPStan for static analysis, custom PHPCS rulesets).
• Consider if:
  • You’re building Drupal 8/9/10 modules/themes and need to enforce community standards.
  • Your team lacks consistent code reviews or struggles with technical debt.
  • You want to automate fixes (e.g., auto-correcting indentation, docblock formats).
  • You’re adopting CI/CD and need to gate code quality (e.g., fail builds on violations).
  • Your editors/IDEs lack built-in Drupal linting (e.g., VSCode without extensions).

How to Pitch It (Stakeholders)

For Executives: "Coder is a turnkey solution to enforce Drupal’s coding standards, saving our team X hours/week on manual reviews and reducing bugs from inconsistent code. By integrating it into our CI pipeline, we’ll catch issues early—like blocking deprecated function usage—while improving onboarding for new hires. The cost? Minimal: a one-time composer require and 15 minutes to configure. The ROI? Fewer production issues, faster releases, and code that’s easier to maintain."

For Engineering: *"This replaces ad-hoc code reviews with automated, actionable feedback. Key benefits:

• Run locally: ./vendor/bin/phpcs flags violations before commits.
• Fix automatically: Auto-corrects formatting (e.g., docblocks, PSR-12) with --fix.
• CI-ready: Fail builds on violations (e.g., GitHub Actions snippet below).
• Editor support: Real-time feedback in PhpStorm/VSCode via plugins. Example CI snippet:

- name: Run Coder
  run: ./vendor/bin/phpcs --standard=DrupalPractice --extensions=php,module web/modules/custom

Downside: Drupal-specific only, but worth it for our stack."*