SSWConsulting / SSWConsulting/SSW.Website

✨ Events Index - Improve upcoming and past event listings

Open
#4,979 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Refinement YakShaver
Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

Description

Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @tiagov8, @isaaclombardssw, @babakamyljanovssw @adamcogan @designbyalex @hveraus @0xharkirat

Hi Team!

  🟥  Watch the video (2 min 40 sec)

  Url from screen share: https://ssw.com.au/events

Pain

Update the Events index page on ⭐ SSW Website (Dev - Next.js) to improve readability and usability for both upcoming and past events. Add a count of upcoming events near the Upcoming Events heading, reduce the size of event blurbs for upcoming events, and improve CTA visibility by using red styling for action buttons and upcoming event countdown labels. Simplify the Past Events section by removing blurbs and CTA buttons so users can scan historical events more easily.

Acceptance Criteria
  1. The Upcoming Events section displays the total number of upcoming events near the section heading (e.g. '10 Upcoming Events' or 'Upcoming Events (10)').
  2. Upcoming event blurbs are truncated to approximately 3 lines or an equivalent character limit.
  3. Users can still navigate to the full event details page from the event card or CTA after truncation.
  4. Upcoming event CTA buttons use the red styling consistent with SSW primary CTA styles.
  5. Upcoming event countdown indicators (e.g. '8 days to go') use a visually distinct red background styling.
  6. Past event countdown/status styling remains unchanged and visually distinct from upcoming events. But it should include the word "WAS" to make it extra clear it's past
  7. Past event cards no longer display event blurbs/descriptions.
  8. Past event cards no longer display the 'Find out more' button.
  9. Past event cards continue to display the event image, title, and key event information.
  10. The updated layout reduces unnecessary scrolling and improves scanability on the Events index page.
  11. Changes are responsive and display correctly across desktop and mobile layouts.
Screenshot

Screenshot
Figure: Upcoming events count on event index

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Events index page in the Next.js website and trace how upcoming and past event cards are rendered. Compare the current layout at https://ssw.com.au/events with the acceptance criteria, then verify that counts, truncation, CTA and status styling, and responsive behavior match for both event groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js
Domain
frontend, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.