Hidev Laravel Package

Product Decisions This Supports

• Build vs. Buy: Reduces need for custom scripting or manual setup of Laravel/PHP project scaffolding, CI/CD pipelines, and release workflows.
• Developer Productivity: Automates repetitive tasks (e.g., composer.json, .gitignore, README.md, CHANGELOG.md, CI configs) to accelerate onboarding and reduce cognitive load.
• Consistency: Enforces standardized project structures and configurations across teams, reducing "works on my machine" issues.
• Roadmap: Enables faster iteration for:
  • Open-source package development (e.g., Laravel add-ons).
  • Internal tooling (e.g., microservices, CLI tools).
  • Legacy code modernization (e.g., migrating from Yii2 to Laravel).
• Use Cases:
  • Bootstrapping: Generate project templates with hidev init (e.g., for new Laravel packages).
  • CI/CD Automation: Pre-configure TravisCI/Scrutinizer with hidev build/hidev test.
  • Release Management: Streamline version bumps (hidev bump) and GitHub releases (hidev release).
  • Code Quality: Enforce PSR-12 via hidev fix (PHP-CS-Fixer integration).
  • Plugin Ecosystem: Extend functionality (e.g., add Laravel-specific templates for AppServiceProvider, routes/web.php).

When to Consider This Package

• Adopt if:
  • Your team maintains multiple Laravel/PHP packages and wants to standardize setup.
  • You frequently bootstrap new projects or onboarding contributors.
  • You lack dedicated DevOps resources but need automated CI/CD and release workflows.
  • Your project uses Composer and GitHub (core integrations).
  • You’re open to YAML-based configuration (low learning curve for PHP devs).
• Look elsewhere if:
  • Your stack is non-PHP (e.g., Node.js, Python) or uses monorepos (e.g., Lerna).
  • You need advanced deployment automation (e.g., Kubernetes, Docker Swarm) beyond PHAR builds.
  • Your team prefers GUI tools (e.g., Laravel Forge, Envoyer) over CLI.
  • You require active maintenance (last release: 2018; though plugins like hidev-php may suffice).
  • Your project is closed-source with no GitHub integration (e.g., private repos without API access).

How to Pitch It (Stakeholders)

For Executives: "HiDev cuts the time to launch a new Laravel package from hours to minutes by automating 80% of the boilerplate—think composer.json, CI configs, and release workflows. For a team shipping 5+ open-source packages/month, this saves ~10 dev-hours/week in setup and maintenance. It’s like having a junior dev who never makes mistakes, but for your infrastructure."

For Engineering: "This is a Composer + GitHub supercharger for Laravel projects. With hidev init, you generate a production-ready project skeleton in one command. Need to bump a version? hidev release handles the CHANGELOG, Git tags, and GitHub release—no more manual steps. It’s plugin-based, so we can extend it for Laravel-specific needs (e.g., auto-generating config/services.php). The YAML config is simple, and the CLI commands replace ad-hoc scripts. Tradeoff: Last updated in 2018, but the core functionality is stable and plugin-driven for customization."

For Developers: "Tired of copying .travis.yml from old projects or manually updating composer.json? HiDev does it for you. Run hidev to auto-fix code style, hidev test to run PHPUnit, or hidev bump to publish a release—all with zero config if you use the hidev-php plugin. It’s like a Swiss Army knife for PHP dev workflows."