Backend Developer Needed – Phase 1.2 (Flask, MySQL, Joomla Integration) -- 3

@amjad2

Hi Aafreenhannan! I’ve reviewed your project and specialize in Python/Flask integrations, particularly with CMS platforms like Joomla. I’ll enhance your existing system by creating public read-only views and ensuring seamless Joomla integration. Let’s discuss how we can move forward efficiently! Best Regards, Amjad Iqbal

@amaank66

I can take over Phase 1.2 of your existing Python/Flask + MySQL Playbill parsing system and extend it cleanly without rebuilding anything from scratch. I understand this is a continuation of a working system, and my focus will be on public read-only views, Joomla integration, and production deployment, exactly within the defined scope. I have strong experience with Flask applications backed by relational MySQL schemas, building public-facing read-only views, search/filter logic, and CMS integrations, including embedding Python systems into CMS-driven sites via APIs and routing so they feel native. For this phase, I will deliver: • Public Actor, Show, and Theater pages with IMDb-style navigation • Actor profiles with discipline-grouped credits, per-show Equity indicators, and a simple USA theater map • Global search and filters (including Equity vs Non-Equity) • Duplicate Playbill detection based on show, theater, and date/year • Joomla integration that reuses the existing Theater database and avoids duplicate records • Full deployment on the client server, Flask environment setup, MySQL wiring, and production verification I’m comfortable working in read-only public systems, writing deterministic logic, and integrating with existing CMS infrastructure without disrupting current data. I can provide a fixed-price quote, clear milestones, and an estimated timeline for Phase 1.2 upon review. Best regards, Amaan Khan L. (CUBEMOONS PVT.)

@reliabletechie

Hi, I’m a Python/Flask developer experienced in MySQL and CMS integrations, including Joomla. I can extend your existing system to deliver Phase 1.2: building public read‑only actor, show, and theater pages, implementing search and filtering, and ensuring duplicate Playbill protection. I’ll also integrate seamlessly with your Joomla site, reusing the existing theater database and deploying the solution on your client server with a fully configured production environment. I understand the need for clean, deterministic data handling and a native Joomla feel for public pages, and I can complete this phase efficiently within your timeline. Kind regards, Shamir

@sundaskdb

Hy, I’ve reviewed your Phase-1 system and scope for Phase 1.2, and this is a clean extension not a rebuild. I’m confident stepping into an existing Flask/MySQL codebase and delivering the public views and Joomla integration exactly as outlined. The focus will be on extending your current data model to public, read-only pages actor, show, and theater profiles with IMDb-style navigation. I’ll implement deterministic duplicate protection at upload time using show, theater, and date logic, then build global search and filters directly on MySQL indexes. I can provide a fixed Phase 1.2 quote and timeline immediately. Happy to start with a short walkthrough of the existing codebase and move straight into implementation.