⭐ Suggestion

Link the event in the main page to a new page related to the specific event, perhaps add also Speaker photos, event registration link and youtube link (if the event is already past).

Additionally, add a back button to go to the main page.

📃 Motivating Example

As a user I'd like to know more info about the listed event

Description

Right after page opening you can see a bit of flickering happing for the event list, which looks to be loaded after the rest of the page, see video:

Maybe we would need a loading phase, in which we will show a loader to the user

Steps to reproduce

• open the List website
• wait for a short period
• you should have experienced a bit of flickering

It would be nice to have the whole site accessible in at least two languages 🇮🇹 🏴󠁧󠁢󠁥󠁮󠁧󠁿
Since we're using next, it should be pretty straightforth https://nextjs.org/docs/pages/building-your-application/routing/internationalization

⭐ Suggestion

Based on previously merged PR #89 .

• FIx comments on merged PR
• Implement TODOs from the same PR:
  • Add event gallery with photos
  • Add event slides link

📃 Motivating Example

We want to improve the event page & add as much features as possible

⭐ Suggestion

When the number of community members exceeds 10/15, it can be annoying to have the whole list on the web page.
Instead, it should be displayed in chunks of 10/12 members, and until members are available, show the "more" button at the bottom of the list.

📃 Motivating Example

We should avoid community members list taking too much content within the web page.

Description of the new feature

We want to add a newsletter so to update community members about new events and stuff.

• Add a panel in the website 'Newsletter' which will ask the user for their email and register it to a 3rd party provider newsletter
• We can use newsletter provider, such as Mailchimp, which has a free plan of 1K monthly emails (use Latina In Tech google account -> ask admin to sign up)

Tech Details

• use the following regex for email: ^([a-z][a-z0-9]{1,13}[_.-]?[a-z0-9]{1,13})@((([0-9]{1,3})([.]{1})([0-9]{1,3})([.]{1})([0-9]{1,3})([.]{1})([0-9]{1,3}))|([a-z0-9]{1,10}[-]?[a-z0-9]{1,10}[.]?[a-z0-9-]{1,10}[.]{1}[a-z]{2,4}))$
  which is safe as per regex DOS
• Try to hide auth token in the source code, perhaps using github secrets

Add a section 'Who are we?' (ita: Chi siamo) with name, image, role & company for each admin.

You can see on linkedin these info:

• https://www.linkedin.com/in/andrea-coluzzi/
• https://www.linkedin.com/in/matteo-boschi/
• https://www.linkedin.com/in/fabrizio-cafolla/
• https://www.linkedin.com/in/fabriziodallabona/
• https://www.linkedin.com/in/francesco-di-muro/
• https://www.linkedin.com/in/antonio-ionta/
• https://www.linkedin.com/in/fabio-adipietro/

It would be nice to have unit and/or e2e testing for our codebase, perhaps just for major features like event list

We should be displayed as the first result on the query "Latina in Tech" in Google search :D
This could be a good starting point
https://nextjs.org/learn-pages-router/seo/rendering-and-ranking/metadata