🐛 Bug - Homepage scroll arrow does not align to next section

[ssw-yakshaver]

Requested by: @Berber-Mama via YakShaver.ai 🦬
cc: @Berber-Mama, @isaaclombardssw, @babakamyljanovssw

Hi Team!

  🟥  Watch the video (59 sec)

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

Pain

The homepage scroll arrow currently scrolls the page down to an incorrect position, leaving the next section partially visible instead of aligning cleanly to the start of the next section. This makes the navigation feel broken and visually inconsistent on the ⭐ SSW Website (Dev - Next.js). Update the scroll behavior so clicking the arrow positions the next section correctly.

Acceptance Criteria

1. Clicking the homepage scroll arrow scrolls the page directly to the start of the next section
2. The next section is fully aligned in the viewport after the scroll completes
3. No partial or awkward positioning occurs after clicking the arrow
4. The scroll behavior works consistently across supported desktop and mobile browsers
5. The scroll animation remains smooth and visually consistent with the homepage design

Reproduce Steps

1. Open the homepage of the ⭐ SSW Website (Dev - Next.js)
2. Locate the scroll arrow on the homepage hero section
3. Click the scroll arrow
4. Observe that the page scrolls to an incorrect position instead of aligning to the next section

Screenshot

Figure: Homepage arrow scrolls to incorrect page position

[designbyalex]

Testing results

Tested the arrow in Chrome DevTools, checking the service cards section is fully in view after the scroll settles:

Viewport	Result
768 × 1024, 1440 × 900, 1920 × 1080	✅
390 × 844, 1280 × 800, 1366 × 768	⚠️ cards clipped 64–110 px
375 × 667	❌ cards clipped 326 px

Heading is always visible, so AC 1 and 5 pass — but AC 2 and 3 don't yet.

At 375 × 667 and 1366 × 768 the content is taller than the viewport (871 px vs 667, 766 px vs 768), so no scroll fix can satisfy them — needs py-24 or the card graphic shrunk. Worth deciding if that's in scope here or a follow-up.

Two PRs target this issue, merge one not both: #4967 (aims at the next block) and #4969 (offset tweak, measured above).

[designbyalex]

✅ Done (mostly) - closed by #4969
A quick and simple improvement, not 100% fix.