WordPress Developer – CBH Live Audio Player + Assessment Expansion

WordPress Developer Needed for CBH Healing Room / Assessment Enhancements We are looking for a WordPress developer to continue work on a custom Christian-Based Healing platform built in WordPress. This is a continuation of an existing custom build. The current system already includes a Deliverance Assessment, custom symptom data, playlist generation, PDF/email output, and a Healing Room / audio player experience. This is not a basic Elementor page builder task. We need someone comfortable working with custom WordPress/PHP, REST API endpoints, JavaScript-based frontend interfaces, JetEngine/custom post types, and staging-site testing. Who We Are / Purpose of the Tool We provide patient care and self-care engagement programs that complement a patient’s medical care. The patients we serve identify with the Christian faith tradition, and our programs are built within that context. The platform includes assessment-based personalized audio playlists, prayer-focused audio experiences, and Healing Room resources designed to support users through short guided audio sessions. Current Site Context The site currently uses: • WordPress • Elementor • JetEngine / custom post types • Custom PHP snippets / custom plugin code • REST API endpoints • JavaScript-based frontend interfaces • Custom Deliverance Assessment workflow • Custom playlist generation • PDF/email generation • Healing Room resource cards • Staging environment for testing The front-end prototypes and design direction for several items are already built or mostly built. We need help wiring these features properly into WordPress, making the backend logic reliable, and confirming everything works on staging. Scope of Work Milestone 1 — Group Prayer Session Cards + Backend Session Fields We need to support Group Prayer Session cards that can be managed from the backend. Scope includes: • Review current CBH Events / Group Prayer Session setup • Add or configure backend fields needed for session display • Allow Admins to assign session title, description, date/time, and audio file where needed • Ensure session cards display correctly on the frontend • Ensure users can select/open a session and be routed to the correct Live Audio Player page • Make sure the selected session data can be loaded by the player Milestone 2 — Simulated Live Audio Player Integration We have already built a front-end prototype for the Live Audio Player experience. The goal is to wire it into the actual WordPress / CBH Events setup. This is not a true live-streaming system. It is a simulated live experience where users feel like they are joining a shared prayer session. Scope includes: • Connect the Live Audio Player to the selected CBH Event / Group Prayer Session • Load the correct MP3/audio file assigned to that event • Support simulated live behavior based on scheduled event start time • If a user joins late, the audio should begin at the correct offset based on the event start time • Example: if the session starts at 2:00 PM and the user joins at 2:04 PM, playback should begin approximately 4 minutes into the audio • Handle session states such as upcoming, live, joined, paused if applicable, completed, and expired where needed • Start participant count simulation only while the session/audio is active • Start avatar animation only while the session/audio is active • Stop, pause, or reset participant count/avatar behavior appropriately when the session ends or is no longer active • Ensure the experience works on desktop, tablet, and mobile Important: The frontend player UI already exists. The main need is integration, timing logic, backend audio assignment, and testing. Milestone 3 — Reminder + Add to Calendar Functionality We need users to be able to save or add a Group Prayer Session to their calendar. Scope includes: • Add reminder / calendar options for Group Prayer Sessions • Support common calendar options such as Google Calendar, Apple Calendar, and Outlook where practical • Ensure the calendar link includes the correct session title, date, time, and description • Confirm timezone handling is reliable • If reminder state is stored on the site, ensure it saves correctly for the user/session • Keep the implementation lightweight and reliable Milestone 4 — Deliverance Assessment Prefill from Previous Submission The Deliverance Assessment already exists. We need to make it easier for returning users to continue or repeat the assessment based on prior selections. Scope includes: • Review how assessment submissions are currently stored • Allow a returning user to load or prefill from a previous submission where appropriate • Preserve selected symptoms, priority values, Top 5 selections, and event_id where needed • Ensure prefilled data does not break the current submission flow • Ensure PDF generation and playlist generation still work correctly after prefill/resubmission • Test the full flow on staging Milestone 5 — Deliverance Assessment Category Expansion The current Deliverance Assessment appears to have some hardcoded category behavior. We need to support additional assessment categories beyond the original four. Current categories include: • Physical • Mental • Emotional • Spiritual Future categories may include: • Relationships / Soul Ties • Habits / Behaviors • Spiritual Disturbances • Occult Involvement • Trauma / Wounds / Brokenness Scope includes: • Review how categories are currently stored, displayed, submitted, and used in the PDF / playlist workflow • Identify category-related areas that are currently hardcoded • Make practical MVP-level updates so additional categories can be added safely • Allow additional categories to be managed from the backend where practical • Support category display order where practical • Support category descriptions where practical • Update the symptoms API so new categories can be returned to the frontend • Preserve cbh_system_order or equivalent ordering for symptoms within each category • Ensure the frontend assessment card grid can display additional categories underneath the first row • Ensure P1/P2 selection continues to work across all categories • Ensure Top 5 selections continue to populate from all selected symptoms • Ensure selection counters and player-time calculations continue to work • Ensure form submission sends the correct symptom IDs, priorities, Top 5 selections, and event_id • Ensure PDF generation and playlist generation continue to work with additional categories • Avoid a full rebuild unless separately approved Frontend layout requirement: • Desktop: keep the existing card-grid layout with four cards across • Category 5, 6, 7, etc. should wrap underneath • Tablet: reduce columns as needed • Mobile: stack into one column • The number of categories should not be hardcoded in the frontend Milestone 6 — PDF / Playlist Workflow Review This milestone is primarily review/testing unless issues are found. Scope includes: • Confirm the PDF output still works after category expansion • Confirm playlist generation still works after category expansion • Confirm Top 5 selections remain accurate • Confirm symptom IDs and audio mappings remain stable • Identify any risk areas before production deployment • Do not rebuild the PDF or playlist workflow unless separately approved Separate Diagnostic Milestone — Elementor Upgrade Crash Review We also need help investigating why the staging site crashes when Elementor is upgraded. Scope includes: • Test Elementor upgrade safely on staging only • Review PHP error logs / WordPress debug logs • Identify whether the issue appears related to Elementor, Elementor Pro, BuddyBoss, JetEngine, custom CBH code, theme conflict, plugin conflict, PHP version, or hosting configuration • Provide a clear recommended fix path • Do not make production changes without approval • If the fix is larger than expected, scope it separately before proceeding Important Notes • Existing frontend prototypes and design direction are already provided • This is mainly custom WordPress/PHP/JS integration work • The frontend should not hardcode symptom/category data long-term • Playlist and assessment logic should remain backend-driven where applicable • All work should be tested on staging before production • Existing assessment submissions, PDF generation, playlist generation, and Healing Room workflow should not be broken • Please communicate clearly if any part of the scope is larger than expected before proceeding What We Will Provide • Existing HTML/CSS/JS prototypes • Current staging pages • Current custom code snippets where needed • Existing REST API structure • Current symptom/category setup • Avatar assets and design direction • Clear milestone notes and acceptance criteria What We Are Looking For • Strong WordPress custom development experience • Comfortable with PHP, custom post types, post meta, REST API endpoints, and JavaScript • Able to work with JetEngine/custom fields where needed • Able to troubleshoot plugin/theme conflicts • Able to test carefully on staging • Able to explain the technical approach clearly • Able to preserve existing working functionality while making improvements To Apply / Confirm Please briefly confirm: 1. Your understanding of the milestone scope 2. Which milestones you consider development versus review/testing 3. Any areas you believe may be technically complex or require additional scoping 4. Your proposed milestone pricing and timeline 5. Your approach for safely diagnosing the Elementor upgrade crash on staging