I run a heavily customised WordPress learning-management platform and I’m planning hundreds of feature requests, fixes and integrations throughout 2026. Each task is scoped so that it can be wrapped up in a matter of days or, at most, a couple of weeks; as soon as one ticket is merged you’ll roll straight onto the next, giving you a reliable pipeline of work. In 2025 I put almost $10 k into development and I expect to exceed that spend in the coming cycle of 2026, so there is real earning potential for a developer who enjoys long-term collaboration. Everything lives in Git and deployments are handled through a staging pipeline, so clean commits and clear commit messages are essential. To get started, review the small onboarding task attached to this listing. It will give us both a feel for code style, communication speed and how you approach existing custom logic. Deliverables for each ticket are straightforward: • well-documented, PSR-12-compliant PHP or front-end code • a pull request that passes our automated test suite • a concise changelog entry explaining what changed and why If you love untangling bespoke WordPress builds and want a steady flow of bite-sized challenges, send me a quick note describing one similar problem you’ve solved, then dive into the attached task. I’m eager to keep momentum high and bring the right coder onboard for the full 2026 roadmap.