Enhance README with Workflow Architecture & Visual Interface Guide

[Nitya-003]

Description

The current README.md provides excellent setup instructions, but it lacks a high-level overview of the AI pipeline and a clear visual distinction between the three available interfaces (CLI, Streamlit, and PySimpleGUI).

---

Proposed Enhancements

1. AI Pipeline Architecture (Mermaid.js)
   We should add a technical flowchart that explains the transition from Computer Vision (OpenCV) to Deep Learning (XCEPTION model) to Web Automation (YouTube).

graph TD
    A[Webcam Feed] --> B[OpenCV: Face Detection]
    B --> C[Pre-processing: Grayscale/Resize]
    C --> D[Model: fer2013_mini_XCEPTION]
    D --> E{Emotion Classified}
    
    E -->|Happy| F[Query: 'Happy Songs']
    E -->|Sad| G[Query: 'Relaxing/Sad Songs']
    E -->|Angry| H[Query: 'Calming Music']
    
    F & G & H --> I[webbrowser: Open YouTube]
    I --> J[User default Browser]
    
    style D fill:#ff6b6b,stroke:#333,stroke-width:2px
    style E fill:#feca57,stroke:#333
    style I fill:#48dbfb,stroke:#333

Loading

2. Interface Comparison Table
   Instead of a list, a table will help users quickly decide which version of the app they want to run.

Interface | Tech Stack | Best For | Command -- | -- | -- | -- Streamlit | Web-based | Beginners / Visual Users | streamlit run ... PySimpleGUI | Desktop App | Lightweight Desktop use | python app_PySimpleGUI.py CLI | Terminal | Servers / Advanced Devs | python cli_main.py

3. Directory Refactoring in README
   The current "Quick Start" mentions paths like code/ui_interfaces/... We should add a Directory Structure section to help contributors navigate the code/ folder and the new_models/ folder easily.

---

Task Checklist

• Visuals: Add the Mermaid diagram to the "How it Works" section.
• UX: Format the "Quick Start" with better code blocks and icons.
• Structure: Create a simplified directory tree to explain where the .hdf5 model and UI scripts live.
• Call to Action: Standardize the "Contribution" section with a clear link to the contribution branch requirement.

---

Why this is important

Users often decide whether to use a tool within 10 seconds of landing on the repo. High-quality visuals and a clear "Interface Choice" table will significantly increase the conversion from "visitor" to "stargazer."

I would love to work on this issue and Submit a PR.

Labels: documentation, ECWOC'26, ECWOC