-
Notifications
You must be signed in to change notification settings - Fork 47
Description
Currently, the site opens directly to specific sections (Passenger page or Admin login). Instead, we need a dedicated homepage that will act as the first screen users see when visiting the site. This homepage will provide clear navigation, branding, and helpful information before users choose their path.
Proposed Changes:
Create a homepage.html as the default landing page that loads when the website URL is accessed, serving as the main navigation hub with direct Passenger access and Admin access requiring login/registration before redirecting to the Admin section for authentication.
The homepage should include:
-
Header – Site name, logo, and a short tagline.
-
Brief Intro Section – Short description of how the website works.
-
Two Main Buttons:
Passenger Access → Directly to Passenger page.
Admin Login → Login/Register → Redirect to Admin page after successful authentication. -
Help & FAQs Section – Common questions and quick answers.
-
Footer – Basic info such as copyright and contact.
Expected Outcome:
First page shown on site load will be the new homepage.
Passenger button → Instantly shows Passenger page.
Admin button → Shows Register/Login → Admin page after successful auth.
Homepage provides clear guidance, branding, and easy navigation for all users.
Tech Stack:
Frontend: HTML, CSS, JavaScript
Backend: Flask (existing authentication system)
[Homepage]
├── Passenger Access → [Passenger Page]
└── Admin Login → [Register/Login] → [Admin Page]
This update will improve first impressions, help new users understand the purpose of the site, and maintain accessibility while still protecting admin functions. It also aligns with open-source goals by making both areas easily accessible for testing and exploration.