Apply feedback and add more better things :)

package.json

@@ -16,8 +16,8 @@
   },
   "dependencies": {
     "@fontsource/montserrat": "^4.5.5",
-    "@fortawesome/fontawesome-svg-core": "^6.1.1",
-    "@fortawesome/free-brands-svg-icons": "^6.1.1",
+    "@fortawesome/fontawesome-svg-core": "6.5.2",
+    "@fortawesome/free-brands-svg-icons": "6.5.2",
     "ant-design-vue": "^4.0.0-rc.6",
     "dayjs": "^1.10.8",
     "pinia": "^2.0.11",
@@ -27,9 +27,9 @@
   "devDependencies": {
     "@cypress/vite-dev-server": "^2.2.2",
     "@cypress/vue": "^3.1.1",
-    "@fortawesome/free-regular-svg-icons": "^6.1.1",
-    "@fortawesome/free-solid-svg-icons": "^6.1.1",
-    "@fortawesome/vue-fontawesome": "^3.0.0-5",
+    "@fortawesome/free-regular-svg-icons": "6.5.2",
+    "@fortawesome/free-solid-svg-icons": "6.5.2",
+    "@fortawesome/vue-fontawesome": "3.0.6",
     "@heroicons/vue": "^1.0.6",
     "@rushstack/eslint-patch": "^1.1.1",
     "@types/node": "^16.11.26",

src/components/Notification.vue

@@ -132,7 +132,7 @@ const getEvent = function (id: string): ScheduleEvent | undefined {
     margin-left: 16px;
     background-color: $primary-color;
     border-radius: 5px;
-    color: $contrast-color;
+    color: #fff;
     cursor: url('../assets/img/rocket-fire.png'), auto;
     font-weight: bold;
     letter-spacing: 1px;

src/data/discover.ts

@@ -0,0 +1,35 @@
+export interface Discover {
+  readonly title: string
+  readonly description: string
+}
+
+export const discovers: Discover[] = [
+  {
+    title: 'Where to eat?',
+    description: `Check out the best places to eat in Barcelona!`,
+  },
+  {
+    title: 'What to visit',
+    description: `Coses com el park guell, la sagrada familia, la rambla, el camp nou, etc`,
+  },
+  {
+    title: 'Tips to move around the city',
+    description: `Movides de la Tmovilitat que no conec perque vaig a tot arreu en moto`,
+  },
+  {
+    title: 'Magical cities nearby',
+    description: `Coses com Sitges, Tarragona, Girona, etc`,
+  },
+  {
+    title: 'Where to stay?',
+    description: `Podem buscar hostels :)`,
+  },
+  {
+    title: 'What to do on the cheap/for free',
+    description: `GL jajaja es broma hem de posar coses chules`,
+  },
+  {
+    title: 'Where to leave your baggage',
+    description: `We can have your baggage in a safe place during the event but if you want to store them before or after the event, you can do it in the lockers: \n - [Locker in the city](https://lockerinthecity.com/)`,
+  },
+]

src/data/judging.ts

@@ -16,13 +16,15 @@ We will have a judging expo on **${formatIntervalInTimezone(
       '5/5/2024 10:15:00',
       '5/5/2024 13:15:00'
     )}**.
-We will assign you a time slot to present your project (one for HackUPC + as many challenges as you participate), you need to go to in front of A3 building and an organizer will assign you to a queue and may give you an estimated time when you will present.
+We will have a judging expo on Sunday ☀️ **from 10:15 to 13:15**, divided in three timeslots of 1h. To present your project, you should follow these steps:\n\n
 
-The presentation can only be **3 minutes** long and with **no slides**, Prezi's or any visual support except your hack. You can check out other projects at any judging room.
-
-The top teams will move on to an additional round of panel judging in the Closing Ceremony.
-
-If you participate in a challenge, you'll have to present at the specific sponsor room, which is independent of the HackUPC judging.`,
+1. Make sure you submitted your project to Devpost before the deadline ⏳!
+2. Watch out for the message on Slack from the organizers, with the timeslot that corresponds to you 📱
+3. When your turn is up, present yourself to the front of the A3 building, where an organizer will add you to the queue 🏢
+4. Wait for the organizer to call up your project and give you your judging room 🙋
+5. Go to the room the organizer told you 🚶🏻‍♀️
+6. Present your amazing project to the judges 🏆
+`,
     size: 'big',
   },
   {

src/data/rules.ts

@@ -24,21 +24,23 @@ These are some highlights of the HackUPC competition rules ⚖️ **Please read
   {
     title: 'The rules of the competition',
     description: `
-1. There is no minimum team size, however, the maximum size is 4 people. There will be 1 prize for each member of the team, independently of the team size.
-2. Teams should be made up exclusively of students (or recent graduates within one year of having graduated) who are not organizers, judges, sponsors, or in any other privileged position at the event. Volunteers are allowed to participate in their free time, accepting the extra difficulty of hacking and volunteering at the same time, but their role won't give them any judging advantage in front of the rest of participants.
-3. All team members should be present at the event. Leaving the venue for some time to hack elsewhere or sleep is fine.
-4. Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
-5. All work on a project should be done at the hackathon.
-6. Teams can use an idea they had before the event.
-7. Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
-8. Teams can work on an idea that they have worked on before (as long as they do not re-use code).
-9. Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
-10. Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
-11. Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.
-12. Participants who asked for a travel reimbursement need to post a project before the deadline in order to get the reimbursement.
-13. Projects that violate the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct) are not allowed.
-14. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct), or other unsporting behaviour.
-    `,
+1. There is no minimum team size, however, the maximum size is 4 people. There will be **1 prize for each member of the team**, independently of the team size.
+2. Every team can only submit up to **one project**, although they can apply to multiple sponsor challenges and win multiple prizes with said project.
+3. Teams should be made up **exclusively of students** (or recent graduates within one year of having graduated) who are not organizers, judges, sponsors, or in any other privileged position at the event. Volunteers are allowed to participate in their free time, accepting the extra difficulty of hacking and volunteering at the same time, but their role won't give them any judging advantage in front of the rest of participants.
+4. All team members should be **present at the event**. Leaving the venue for some time to hack elsewhere or sleep is fine.
+5. All team members should be **accepted** into the hackathon by the organization and registered into the online platforms used before and during the event.
+6. All team members should be **reachable** by any member of the organization team during the event.
+7. Teams can of course gain **advice and support** from organizers, volunteers, sponsors, and others.
+8. All work on a project should be **done at the hackathon**.
+9. Teams can use an **idea they had before the event**.
+10. Teams can work on **ideas that have already been done**. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
+11. Teams can work on an **idea that they have worked on before** (as long as they do not re-use code).
+12. Teams can **use libraries, frameworks, or open-source code** in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
+13. Adding **new features to existing projects is allowed**. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
+14. Teams must **stop hacking once the time is up**. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.
+15. Participants who asked for a travel reimbursement need to **post a project before the deadline** in order to get the reimbursement, check all the information in the [travel reimbursement section](/travel).
+16. Projects that violate the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct) are not allowed.
+17. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the [Code of Conduct](https://legal.hackersatupc.org/hackupc/code_of_conduct), or other unsporting behaviour.`,
     size: 'big',
   },
 ]