SSWConsulting / SSWConsulting/SSW.Website

🐛 Fix logo carousel scroll speed on .NET 8 consulting page

Open
#3,536 0 comments 0 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: @Calinator444 via YakShaver.ai 🦬
cc: @Calinator444, @wicksipedia, @isaaclombardssw
Hi Team!

Watch the video

Pain

The logo carousel on the .NET 8 consulting page has a bug where the scroll speed is affected by the number of logos in the carousel. The animation speed should remain consistent regardless of the number of logos present.

Acceptance Criteria
  1. The logo carousel scroll speed remains consistent regardless of the number of logos.
  2. The carousel animation does not slow down when logos are removed.
  3. The carousel maintains a smooth and uniform scroll speed with any number of logos.
Reproduce Steps
  1. Navigate to the .NET 8 consulting page on the SSW website.
  2. Observe the scroll speed of the logo carousel with 10 logos.
  3. Remove some logos from the carousel.
  4. Observe that the carousel animation gets gradually slower as the number of logos decreases.
  5. Verify that with only one logo, the carousel animation slows to a crawl.
Screenshot

Screenshot
Figure: Create an issue on the SSW website backlog.

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

Open the .NET 8 consulting page in the SSW.Website project and inspect the logo carousel implementation. Reproduce the speed change with 10 logos and then with fewer or one logo. Done means the carousel keeps a smooth, uniform speed regardless of the number of logos.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.