phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Moodle PHP Developer Needed for Plugin Development

  • Posted:
  • Proposals: 29
  • Remote
  • #4424305
  • OPPORTUNITY
  • Expired
Daniel B.Mohsin A.John B.Michael A.Rahul C. + 24 others have already sent a proposal.
  • 6

Description

Experience Level: Expert
Estimated project duration: More than 6 months
We are looking for an experienced PHP Developer with Moodle LMS experience to help us with several development tasks.

Project scope (first tasks):
- Develop Moodle plugin (custom functionality).
- Integrate external APIs (payment system, chatbot, biometric verification).
- Adjust Moodle templates and styles (minor frontend changes).
- Custom modifications in user registration & documents.

Requirements:
- Strong PHP & MySQL knowledge.
- Experience in Moodle plugin development.
- API integrations (REST, JSON).
- Basic frontend (HTML, CSS, JS).

What we offer:
- This project includes several tasks (plugins + API + UI fixes).
- If the collaboration goes well, we will have continuous projects and new features to work on.
- Please share examples of your Moodle-related work (plugins, integrations, LMS projects).

Looking forward to long-term cooperation with the right candidate.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Owen B.

    Can you give some details of the custom development you need and the APIs you are looking to integrate with, so I can get an idea of the scope of the initial phase?

    Any details you can give of the minor changes to the templates, etc would also be helpful.

  • Henry T.

    Subject: Quick scoping questions + MVP starting point for your new GHL system

    Hi Simon — before I propose a final scope, could you please confirm a few items so we size this correctly?

    1) Business & offers

    What single core offer (product/service) should our first funnel promote?

    Target countries/time zones & languages?

    Expected daily/weekly lead volume for phase 1?

    2) Compliance & sending policy

    GDPR/TCPA consent approach (double-opt in? consent copy already available)?

    SMS/WhatsApp needed now, or email-only for MVP?

    Quiet hours, frequency caps, and unsubscribe policy?

    3) Domains, email & phone

    Do you have a sending domain ready? Can we authenticate it (SPF/DKIM/DMARC)?

    New or shared IP? Any prior reputation/warmup history?

    Phone provider preference (LC Phone/Twilio) and A2P 10DLC/WhatsApp status?

    4) Tracking & attribution

    Do you already run Meta/Google ads? Should we implement GA4 + Pixels + CAPI from day one?

    UTM naming standards in place?

    5) Data & CRM

    Any existing contacts to import? Required fields/tags and dedupe rules?

    Desired CRM pipeline stages for opportunities?

    6) Assets & templates

    Who provides landing-page copy, emails, SMS messages, images?
    (I can draft “good-to-start” templates if needed.)

    7) Calendars & scheduling

    Booking model (single rep / round-robin / by team)?

    Meeting tools to integrate (Google/Outlook/Zoom)?

    8) Integrations (if any)

    Payments (Stripe), helpdesk, external CRM/ERP, Make/Zapier — which are must-haves for phase 1?

    9) Team & governance

    How many users at launch? Required roles/permissions?

    Need content approval workflow/audit trail in phase 1?

    10) Success criteria

    Which KPIs prove success in the first 2–4 weeks? (e.g., leads, opt-in rate, bookings, show-ups)

    Proposed starting point — “one golden path” MVP

    Goal: get real leads and live data fast, then iterate.

    MVP scope (candidate):

    Sub-account setup, domain & email authentication (SPF/DKIM/DMARC)

    1 funnel + form (or survey) + calendar booking

    1 automated workflow (email + optional SMS), tagging & basic nurturing

    CRM pipeline with stages; simple dashboard

    GA4 + Pixels (and CAPI if ad accounts are ready)

    Handover playbook + snapshot for reuse

    Effort for MVP: ~30–50 hours (includes setup, testing, and a basic template set).
    Please confirm if you accept this MVP as the starting milestone.

    Beyond MVP — full system range (for planning)

    Template library, list hygiene, frequency caps, multi-brand snapshot: ~80–120 hours total (incl. MVP)

    Plus governance & external integrations (roles/approvals/Stripe/Make/Zapier, monitoring): ~120–200 hours total (incl. MVP)

    (Actuals depend on asset readiness, compliance approvals, and the number of brands/teams.)

    If the above looks right, I’ll draft the exact MVP task list and a not-to-exceed cap for phase 1. Looking forward to your answers!
    Cheers,
    Henry

    Gani S.04 Sep 2025

    Hi Henry,

    Thanks for your detailed scoping message. Just to clarify: we already have a working e-learning system built on Moodle, so we don’t need a new MVP funnel setup. Our project is about customizing and extending Moodle with specific integrations and features.

    Best regards,
    Gani

    Henry T.04 Sep 2025

    Hi Gani,

    Thanks for clarifying — it’s very helpful to know your Moodle system is already live. To ensure we size the work correctly and avoid surprises later, I’d like to confirm a few technical details. These points may sound small, but they directly affect development effort, plugin compatibility, and long-term maintainability:

    Moodle environment

    Which Moodle version is running (3.x or 4.x)?

    Do you already have a staging/dev environment for testing plugins?
    (Reason: Plugin APIs and database structures vary by version; without a test environment, changes risk affecting live users.)

    Priority of tasks

    Among plugins, API integrations, template changes, and registration/document modifications — which one is the first milestone?
    (Reason: This helps me focus development effort and set a clear delivery order.)

    External APIs

    For payment, chatbot, and biometric verification: which providers are confirmed? Do you have API documentation and sandbox access?
    (Reason: Each API has different integration complexity; e.g. Stripe vs. local gateways, or Google Dialogflow vs. a custom chatbot.)

    User registration & documents

    Are modifications limited to adding extra fields, or do you need workflow logic (approval steps, ID verification, digital signatures)?
    (Reason: Simple field extensions take hours, but workflow engines require much more planning.)

    Templates & UI

    When you mention “minor frontend changes,” do you mean CSS/style adjustments or deeper theme/template overrides?
    (Reason: Styling tweaks are quick; theme-level overrides require regression testing.)

    Delivery & version control

    Do you prefer code delivery through a Git repository (GitHub/GitLab) or packaged ZIP uploads?
    (Reason: Version control ensures smooth future updates and easier collaboration.)

    If you could confirm these, I can propose a phased plan (with hours per milestone) and ensure the first delivery is aligned with your most urgent needs.

    Best regards,
    Henry