Move Views from Components into Base System

[mariobehling]

As part of the Eventyay Unified System, we are consolidating functionality from multiple sub-projects (eventyay-tickets, eventyay-talk, eventyay-video, etc.) into the base system. Currently, many views still reside in individual components. This causes duplication, inconsistent UX, and makes maintenance harder. To complete the unification, we need to migrate all views into the base system, while keeping components focused on their logic (APIs, services, utilities).

Goal

• Move views from sub-components into the base system.
• Ensure all views follow the unified design system (VueJS 3).
• Maintain feature parity while consolidating.
• Track progress for each migrated view here.

Views To Be Moved

Common views at eventyay.com/[here] [Quan]

• Unified Login (Gagan)
• Registration Views
• Event Dashboard (Organizer)
• Attendee Dashboard
• Settings (Profile, Organization, Teams)

Ticketing (from eventyay-tickets) at eventyay.com/tickets/ [Srivatsav]

• Ticket Purchase Page (/tickets)
• Ticket Checkout Page (/checkout)
• Ticket Confirmation Page (/confirmation)
• Ticket QR Scanner View
• Order History / My Tickets Page

Talks & Schedule (from eventyay-talk) at at eventyay.com/talk/ [Gagan]

• Schedule Overview (/schedule)
• Session Detail Page
• Speaker Profile Page
• Speaker Dashboard (CFP Management)
• Organizer Schedule Management View
• Session Submission Form

Video (from eventyay-video) at at eventyay.com/video/ [Suhail]

• Embedded Video Session View
• Speaker Backstage / Control View
• Live Interpretation Selection View
• Recording Archive / Playback Page

Badge System [Yakshit] as part of ticketing component

• Badge Template Designer
• Badge Preview & Print View
• Badge Export / Download Page

Exhibitor Plugin [Yakshit] as part of ticketing component

• Exhibitor Directory / List View
• Exhibitor Detail Page

Migration Steps [Yakshit]

1. Identify and copy view logic & templates from components.
2. Refactor views to use unified base system components (VueJS 3).
3. Replace component-level routing with base system routing.
4. Verify API integration (tickets, talks, video).
5. Update tests and documentation.

Tracking

We will update this issue as each view is migrated.
If needed, create sub-issues for larger refactorings and link them here.

[hongquan]

After #860 , some views are moved back to "/common/". I will move them again (to root "/") after #863