Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restyling event page & link to event list #89

Merged
merged 7 commits into from
Jan 2, 2024

Conversation

coluzziandrea
Copy link
Member

@coluzziandrea coluzziandrea commented Jan 1, 2024

📚 Description

Closes #36

What

  • Restyled Event Page
  • Linked Event list to event detail page
  • Added speakers, tags and full description for each event
  • Added signup URL for incoming event & eventbrite link to event page
  • Restyled Sponsor section, adding a bit of opacity and hover effect

Why

The user didn't have a way to enter the event page but manually write the URL

🖼 Screenshots/Recordings

image
image
Screenshot Capture - 2024-01-01 - 11-47-25
image

Desktop new experience

screen-capture.webm

Phone new experience

screen-capture.2.webm

📝 To Do

  • Add event gallery with photos
  • Add event slides link

{ locale: 'it' }
);

const EventAction = ({
Copy link
Contributor

@Undermaken Undermaken Jan 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in order to avoid defining this component on every renderer, could it be moved outside EventActions as a standalone component (we could keep it in the same file)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great tip

[events]
);
const nextEvents = useMemo(
() => sortEvents(filterComingEvents(events)),
[events]
);

const hasMorePastEvents = events.length > MAX_PAST_EVENTS + nextEvents.length;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I didn't get the logic but I can't understand why nextEvents should be involved in this condition

Suggested change
const hasMorePastEvents = events.length > MAX_PAST_EVENTS + nextEvents.length;
const hasMorePastEvents = filterPastEvents(events).length > MAX_PAST_EVENTS;

Am I losing something?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, my bad 👍

@Undermaken Undermaken merged commit 639070a into latina-in-tech:main Jan 2, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Event Page
2 participants