[Bash2.0] Use-case cards look clickable but have no link
Nobody has claimed this yet.
- Dominant language
- Astro
- Stars
- 155
- Forks
- 176
- Avg merge
- 1d 20m
- Merged PRs (30d)
- 192
Description
Describe the issue
On the industry use-case pages, the cards under sections like "Infrastructure & Platform Orchestration" and "Cybersecurity & SOC Operations" react to hover, they lift up, get a shadow, and show a blue border. That makes them look clickable, but nothing happens when you click. There's no link behind them.
So people hover and click expecting to go somewhere, and get nothing.
Steps to reproduce
1. Go to kestra.io/use-cases/public-services.
2. Scroll to the cards, for example "Incident Response & Threat Containment".
3. Hover over a card, then click it.
Actual behaviour
On hover the card lifts, gets a shadow, and its border turns blue, all the usual "you can click me" cues. But the card is just a plain block with no link, so clicking does nothing.
It's the same on every industry use-case page: healthcare, financial-services, retail, automotive, public-services, and software-providers. Each has 12 of these cards, none of them linked.
Expected behaviour
- If the cards are meant to go somewhere, add the links.
- If not, drop the hover effect so they don't look clickable.
Environment
- Site: kestra.io (use-cases pages)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the cards on the public-services use-case page with the corresponding cards on healthcare, financial-services, retail, automotive, and software-providers pages. Inspect the card behavior and determine whether the intended outcome is linked cards or non-clickable styling; done means the cards no longer suggest an unavailable action, and the behavior is consistent across all listed pages.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100