Feature/add back to top button

[Asin-Junior-Honore]

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Steps to QA

Tier (staff will fill in)

• Tier 1
• Tier 2
• Tier 3
• Tier 4

[optional] What gif best describes this PR or how it makes you feel?

[netlify]

✅ Deploy Preview for opensauced-landing ready!

Name	Link
🔨 Latest commit	4528d43
🔍 Latest deploy log	https://app.netlify.com/sites/opensauced-landing/deploys/6649b596365f8a0008b8ff69
😎 Deploy Preview	https://deploy-preview-281--opensauced-landing.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 91 (no change from production) Best Practices: 92 (no change from production) SEO: 83 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bdougie]

The button is on the wrong page. I'd expect to see it while reading a long article https://opensauced.pizza/blog/how-we-saved-thousands-of-dollars-deploying-low-cost-open-source-ai-technologies

[Asin-Junior-Honore]

@bdougie, oh yeah, that's true. Sorry, I placed it on the main blog page (http://localhost:3001/blog). Should I put the button only on the specific blog post page (http://localhost:3001/blog/how-we-saved-thousands-of-dollars-deploying-low-cost-open-source-ai-technologies), or should I include it on both the main blog page and the specific blog post page?

[bdougie]

Yes. Only on blog post page.

I'd expect to see it while reading a long article

[Asin-Junior-Honore]

@bdougie all done sir 🙇

[bdougie]

I won't be able to view this from anything but mobile for awhile, but placement of the button is not working. I'd suggest centering it.

I'd also suggest providing screen shots and a description to the PR.

Please read this blog post. https://dev.to/opensauced/the-secret-recipe-to-getting-your-pull-requests-reviewed-and-merged-faster-1fag

[Asin-Junior-Honore]

Hey, @bdougie
I apologize for any confusion caused. Upon revisiting the code base, I discovered that the tailwind.config.js file had been modified with different screen size configurations. This was preventing the button from adjusting properly with the initial logic I used.

However, I have rectified the issue. Here is the corrected and well-placed "Back to Top" button for mobile screen sizes and larger ones:

large-screen

mobile-screen