fix: Tailwind apply usage for custom scrollbar

[gocanto]

Summary

• remove the non-Tailwind custom-scrollbar utility from the blog stylesheet to stop Tailwind from failing the build

Testing

• make build-ci (fails: docker: command not found)

---

https://chatgpt.com/codex/tasks/task_e_68f840e0ae0083339646a0214e02bbe3

Summary by CodeRabbit

• Style
  • Improved scrollbar styling consistency in the recommendations list for better cross-browser support while preserving smooth scrolling.
  • Updated recommendations list markup to ensure consistent spacing and visual behavior across pages.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

CSS: removed the custom-scrollbar utility from the .recommendations-list rule in src/css/support/blog.css. Template: src/partials/ResumePageSkeletonPartial.vue now adds the custom-scrollbar class to the recommendations list container.

Changes

Cohort / File(s)	Summary
CSS Utility Update src/css/support/blog.css	Removed custom-scrollbar utility from the .recommendations-list selector; scroll-smooth retained.
Template class change src/partials/ResumePageSkeletonPartial.vue	Added custom-scrollbar and recommendations-list classes to the recommendations list container (class list now includes recommendations-list custom-scrollbar space-y-8).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Refine post markdown scrollbars #63: Refactors and centralizes .custom-scrollbar styles and scrollbar variables — directly related to toggling that utility.
• fix: Increase recommendations section height #128: Modifies recommendations-list sizing and class usage; touches the same component-level styling.
• fix: Tailwind apply usage for custom scrollbar #130: Edits the same .recommendations-list rule in src/css/support/blog.css by removing the non‑Tailwind custom-scrollbar utility.

Poem

🐰 I hopped through lines of style and class,
I nudged a scrollbar out, then nudged it back, alas!
Smooth paths remain where users glide,
A tiny change — a tiny stride. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Fix Tailwind apply usage for custom scrollbar" is partially related to the changeset. It correctly identifies the core elements of the change—Tailwind, apply usage, and custom scrollbar—and accurately conveys that this is a fix for a related issue. However, the title is somewhat vague about the specific solution; it doesn't clearly communicate that the fix involves removing the non-Tailwind custom-scrollbar utility that was breaking the build. While a reader might expect the fix to be about improving how Tailwind applies the custom scrollbar, the actual change is to eliminate the problematic utility entirely. Despite this lack of specificity, the title is not misleading and does reference a real aspect of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b3ab00a and f66355c.

📒 Files selected for processing (1)

• src/partials/ResumePageSkeletonPartial.vue (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @gocanto, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a build failure by modifying a CSS file. Specifically, it removes a non-Tailwind utility from an @apply directive within the blog.css stylesheet, which was causing the Tailwind build process to fail. The change ensures compatibility with Tailwind's parsing rules while maintaining the intended scroll-smooth behavior for the recommendations list.

Highlights

• Tailwind CSS Build Fix: Removed the custom-scrollbar utility from the blog.css stylesheet to resolve build failures caused by Tailwind's @apply directive not recognizing it.
• CSS Styling Adjustment: The .recommendations-list element in blog.css no longer applies the custom-scrollbar utility, relying solely on scroll-smooth for scrolling behavior.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes a build failure in Tailwind by removing the custom-scrollbar utility, which is not a standard Tailwind class, from an @apply directive. The change is straightforward and effectively resolves the issue described. The code is now cleaner and adheres to Tailwind's usage patterns.