From 756940299adcdcb4fc93b8ed0d017a098ccb87af Mon Sep 17 00:00:00 2001
From: IanoNjuguna <inc3099@gmail.com>
Date: Wed, 14 Oct 2026 15:44:33 +0300
Subject: [PATCH] fix(website): make the homepage card link hover class
 actually match

HomepageFeatures passed className="featureCardLinks" as a plain string while
the rule lives in the CSS module as .featureCardLinks:hover. CSS modules hash
local class names, so the emitted selector is .featureCardLinks_kdMv:hover and
the plain-string element never matched it: the hover underline reset was dead
code and the three homepage cards underlined on hover.

Pass styles.featureCardLinks so the element carries the hashed class.

Measured on the deployed bundle with the hover state forced through CDP, which
is also the proof the fix works rather than just compiles:

  as shipped, :hover forced          -> text-decoration: underline
  same node with the module class    -> none
  resting state                      -> none

A repo-wide sweep for the same shape (plain-string class names colliding with
CSS-module local names) found this as the only instance.

Refs #323
---
 website/src/components/HomepageFeatures/index.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/src/components/HomepageFeatures/index.tsx b/website/src/components/HomepageFeatures/index.tsx
index 6e2a170c..ea9827df 100644
--- a/website/src/components/HomepageFeatures/index.tsx
+++ b/website/src/components/HomepageFeatures/index.tsx
@@ -55,7 +55,7 @@ const FeatureList: FeatureItem[] = [
 function Feature({ title, description, image, link }: FeatureItem) {
   return (
     <div className={clsx("col col--4")}>
-      <Link className="featureCardLinks" to={link}>
+      <Link className={styles.featureCardLinks} to={link}>
         <div className={styles.featureCard}>
           <div className={styles.featureContent}>
             <div className={styles.featureImageContainer}>