How sriya-singh/eventflow works
Project Overview
• EventFlow is a web application for event planning and management.
• It uses HTML, CSS, and JavaScript for the frontend, Firebase for authentication and database (Firestore), and the Gemini API for AI-driven email generation.
• The application comprises several standalone pages (e.g., home, profile, invite, createNew, upcoming) that share common elements like a navbar and overall styling.
Main Components
a. Frontend/UI Components:
• Pages: index.html, home.html, createNew.html, invite.html, profile.html, upcoming.html.
• Styles: Each page has its own CSS (e.g., home.css, createNew.css, invite.css, profile.css, upcoming.css) plus a global style.css for overall styling.
• JavaScript files: Corresponding JS files for individual pages (e.g., home.js, createNew.js, invite.js, profile.js, upcoming.js) to handle UI interactions.
• Navbar Component: Represented by navbar.html and navbar.css, this is the shared navigation element across the application.
b. Backend Integration and External Services:
• Firebase:
• firebaseauth.js handles user authentication.
• Firebase services are used for authentication and Firestore for database management (storing event data, guest lists, funding logs, etc.).
• AI Email Generation:
• Gemini API integration for AI-powered personalized email generation.
Relationships and Interactions
• The Frontend/UI components are responsible for collecting user inputs on events, scheduling, checklists, guest management, etc.
• The JavaScript modules, including firebaseauth.js, interact with Firebase services to authenticate users and perform CRUD operations on event data.
• When generating personalized emails, the frontend or a dedicated module will call the Gemini API to get AI-generated content.
• The Navbar is a shared element that provides navigation between the various pages.
• Data flows from the user’s browser (via HTML forms and UI interactions) to Firebase for secure authentication and data storage, and outward requests are made to the external Gemini API for generating email content.
Architectural Patterns and Design Principles
• Separation of Concerns: Clear division between the UI (HTML/CSS/JS) and backend functions (Firebase authentication, Firestore interactions, AI API integration).
• Modular Design: Each page (home, createNew, etc.) is implemented as separate modules with its own style and script, making it easier to maintain.
• Client-Server Architecture: While the UI runs on the client side, backend services like Firebase and the Gemini API serve as the server-side components.
• External Service Integration: Emphasizes RESTful API calls between the client and external services (Firebase and Gemini).