'bandfront-player' WordPress Plugin Modernisation

'bandfront-player' WordPress Plugin Modernisation

Please not that I am an Autistic Developer - Please do not bombard me with AI proposals when you do not have the experience! Some of the tasks will be completed by me :)

GitHub: https://github.com/100mountains/bandfront-player
Works with: https://github.com/100mountains/bandfront (child theme for storefront)
Live Demo: https://therob.lol/

Seeking experienced WordPress/PHP developer with fluent English for comprehensive plugin modernisation. Must read documentation thoroughly - templated proposals are not appreciated.

Project Status
Open-source music commerce plugin (~7,000 lines PHP) that transforms WooCommerce into a Bandcamp-style platform. Significant architecture work completed - now focusing on code quality, performance, and modern standards, removing support for outdated audio libs.

Tasks

#### 1. Core Code Modernisation (Priority 1)
• 25 PHP files requiring modern standards refactoring
• Reduce code bloat while maintaining readability
• Input sanitisation audit (targeted areas identified)
• Remove redundant options between product/global settings
• Design Decision needed on main page: Track titles on shop page vs. Bandcamp-style approach


#### 2. Player Modernisation (Priority 2) - MAJOR OVERHAUL
Critical: Complete CSS skinning modernisation required

Current Problems (MUST FIX):
• ❌ Sprite-based icons (2010s era) - controls-ted.png, controls-wmp.png
• ❌ Custom font dependencies - Guifx_v2_Transports.woff causes accessibility issues
• ❌ Hardcoded absolute positioning - breaks mobile responsiveness
• ❌ Missing ARIA labels and keyboard navigation
• ❌ Touch targets potentially bad for mobile (under 44px minimum)

Required Modernisation:
• Replace sprite images with CSS-only icons (triangles, bars, shapes)
• Implement CSS custom properties for easy theming
• Convert to flexbox layout - responsive, mobile-first
• Add ARIA accessibility - screen reader and keyboard support
• Touch-friendly controls - 44px minimum touch targets
• Remove dependencies - no external fonts or images needed

Player Engine Decisions:
• Keep MediaElement.js (architecturally sound, just needs modern skinning)
• Keep Compact Audio Player (functional, if basic)
• Remove jPlayer integration (security closed 2022)
• Remove HTML5 Audio Player (incompatible now)
• Remove CPMedia player (looks outdated)
• Consider Plyr.js addon for lightweight drop-in replacement for jplayer
• Consider WaveSurfer.js addon for waveform overlays over album covers

#### 3. WordPress.org Compliance (Priority 3)
• Nonce verification across all forms/AJAX
• Capability checks on admin functions
• SQL injection prevention audit
• XSS protection verification
• Plugin directory standards compliance

#### 4. Performance & Testing (Priority 4)
• Database query optimization
• Conditional asset loading (CSS/JS only when needed)
• Caching strategy review and transient optimization
• Multi-browser testing (Chrome, Firefox, Safari, Edge)
• Mobile responsiveness verification
• Error handling for missing audio files

Technical Requirements

Current Architecture:
• 25 PHP files requiring review and modernization
• 10 core classes with modern OOP structure
• MediaElement.js integration (WordPress core)
• WooCommerce + Storefront child theme compatibility

Key Classes:
includes/class-bfp-admin.php # Admin interface
includes/class-bfp-player-renderer.php # Template system
includes/class-bfp-audio-processor.php # File processing
includes/class-bfp-woocommerce.php # WC integration

Accessibility Notes:
• Leverage WordPress core accessibility features where possible
• MediaElement.js has built-in ARIA support to utilize
• Focus on keyboard navigation and screen reader compatibility

Developer Requirements
• Fluent English - extensive documentation to review
• WordPress plugin development experience (hooks, custom post types)
• Modern PHP practices (OOP, PSR standards, security)
• WooCommerce development knowledge essential
• Audio/media handling experience preferred
• Accessibility best practices familiarity

Available Resources
• Comprehensive documentation (Google Doc + GitHub)
• Live development server access (therob.lol)
• 32GB test server option available
• Full deployment automation
• Detailed modernisation roadmap

Discussion Points
• Shop page track titles: Remove option and hardcode vs. Bandcamp-style display
• Audio plugin prioritization: Which integrations to maintain
• Skin consolidation: Which 2 of 3 skins to keep
• Performance optimization priorities

Budget reflects open-source nature. Demonstrate documentation comprehension in your proposal.

please also see Google doc with more info: https://docs.google.com/document/d/17TUtBsTGZKdl735vyRH-LwxP8D32Nmc3KG_yY1s1pCU/edit?tab=t.0