owltide/components
Hornwitser 7a95d6c3c4 Use prefix notation for component names
Start component names with the kind of element it creates on the page
(button, input, table, card, etc), then follow it with an hierarchy like
set of parts describing what part of the system it operates on.

This makes related components stick together in the directory listing of
components and auto-complete work better.
2025-06-17 22:29:16 +02:00
..
AssignedCrew.vue Refactor to use ClientSchedule on client 2025-06-14 19:22:53 +02:00
ButtonLogOut.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
CardEvent.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
Header.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
PushNotification.vue Use a pinia store to manage session state 2025-05-24 18:18:27 +02:00
TableScheduleEvents.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
TableScheduleEventSlots.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
TableScheduleLocations.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
TableScheduleRoles.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
TableScheduleShifts.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
TableScheduleShiftSlots.vue Use prefix notation for component names 2025-06-17 22:29:16 +02:00
timetable-terminology.png Port application from Next.js to Nuxt 2025-03-05 15:36:50 +01:00
Timetable.vue Refactor to use ClientSchedule on client 2025-06-14 19:22:53 +02:00