Laravel Blade Medical UI Revamp

Project Description

We are looking for an experienced Laravel Blade frontend developer to refactor an existing medical report editing interface into a modern, structured clinical workspace.

This is NOT a simple UI redesign.
It is a complex UI refactor with strict constraints, and requires strong attention to detail and ability to work with an existing codebase without breaking functionality.

⸻

Objective

Transform the current single-column page into a two-column clinical workspace with:
• a dominant TinyMCE editor
• a structured right sidebar with clinical data
• an improved workflow for medical reporting
• a cleaner and safer user experience for doctors

⸻

Tech Stack
• Laravel (Blade templates)
• Vanilla JavaScript (no frameworks required)
• TinyMCE (already integrated — must not be modified)

⸻

CRITICAL CONSTRAINTS (READ CAREFULLY)

This project has non-negotiable technical constraints:
• DO NOT modify TinyMCE initialization or lifecycle
• DO NOT create new editors
• DO NOT move the editor into hidden containers
• DO NOT introduce backend changes (controllers, routes, DB)
• DO NOT rewrite existing features (attachments, save logic, etc.)
• You can ONLY refactor the UI using Blade + CSS + minimal JS
• You must preserve ALL existing functionality

Breaking TinyMCE or existing logic = immediate rejection.

⸻

Scope of Work

You will:
• Implement a 2-column layout (70% / 30%)
• Create a sticky top bar with actions (Save, Finalize, etc.)
• Build a tab system (AI / Output / History)
• Move existing sections into the correct positions
• Implement a right sidebar with 3 cards only:
• Quick structured data
• Fetal biometry (UI only)
• Attachments (existing system, must be preserved)
• Improve usability without changing underlying logic

⸻

Important Concepts

This system is NOT a simple form.
• Clinical data is stored as structured JSON (payload_json)
• The editor uses dynamic placeholders
• The UI must not convert structured data into static text
• The report has a finalization (medico-legal) state

⸻

Attachments (HIGH RISK AREA)

The attachments system is already implemented.

You must:
• keep upload, delete, preview, filters working exactly as-is
• move the UI into the sidebar without breaking anything
• NOT rewrite the logic

If changes outside Blade are needed → you must stop and report.

⸻

Design Reference

You will receive:
• Full technical specification (very detailed)
• Interactive HTML preview (target layout)
• PDF visual reference

You must follow them strictly.

⸻

Ideal Candidate

We are looking for someone who:
• has strong Laravel Blade experience
• is comfortable working with existing legacy code
• understands UI refactoring without breaking logic
• pays attention to details and constraints
• communicates clearly if something is unclear

⸻

Not suitable for
• beginners
• developers who want to “rewrite everything”
• developers who rely on frameworks (React, Vue, etc.)
• developers who ignore constraints

⸻

Deliverables
• Updated Blade files
• Short summary of implemented changes
• List of any blocked issues or dependencies
• Screenshots (desktop + mobile)

⸻

Important

If something in the UI requires backend changes, do not guess.
Stop and ask.

⸻

If you read everything, start your proposal with:
“I understand the TinyMCE constraints”