Adding Elegant Shadows with React to Invite Users to Scroll
By keeping your content in a box with a reasonably small height, you risk keeping hidden a part of your content. Users may not know that they can scroll down. How do you make sure they don't miss anything? At Qovery, we love to find elegant and subtle designs that encourage users to better use our product. In this article, I will explain how I added a Shadow effect to invite our users to scroll down content. Let's go!
Before we start, let's quickly illustrate what we are talking about. Yes, this is what you see below. A simple shadow effect 🙂. (It's more complex than what it looks like - keep reading).
The thing is that adding this shadow can be a little bit tricky because you want it to be here at the beginning. Then if you scroll, you want to have it on top and bottom. And if you reach the bottom, you want to hide the bottom shadow.
After implementing it the first time with a bad developer experience on our v2, we have decided to redo it from scratch on our React v3.
In this article, you will learn how to do it and what we added to the common implementation you usually find everywhere on google.
A First Glimpse Into the Developer Experience
At the end of this article, you should have been able to use this component as quickly as this:
Your
Very
long
long
long
long
long
long
long
long
content
You have to wrap your content with the "<ScrollShadowWrapper>", giving it a max height; that’s it!
What our Implementation Improves Compared to the One we Found Anywhere Else
Shout out to Marius Ibsen, that created a pretty elegant way to detect when we need the top and the bottom shadow. He documented that in his medium article.
The problem with his implementation is not in the detection but in the shadow itself. His shadows are done with "box-shadow inset", and the problem with the box shadows is that they are pretty ugly, and you don’t have any control over them.
So instead of using a hook as he does, we use a WrapperComponent to embed all the improvements we want. And our improvements are on the count of 2.
One is about the shadows, but another, which we will cover a little bit later, provides an auto re-computation of the shadow presence when the content evolves. If the content gets bigger for any reason (async loading, filtering, …), the shadow presence must be re-asserted.
Our Own Beautiful Shadows
To implement the shadows, we used two div that stick to the top and the bottom of the wrapper with the "sticky" CSS property.
We use Tailwind in our example, but you can use whatever you want for your own implementation. As long as you set your blocks as "sticky" and, respectively "top-0" and "bottom-0"
Another trick to keep the shadows on top of the content
By default, sticky keeps your block in the flow, so if your shadow is 16px tall, it will add 16px on top of your content, and you won’t have the desired effect; your shadow will be floating in the middle of nowhere instead of being on top of the content.
What you want to do, is to remove the size of the shadow from the flow, you want the shadow, to be on top of your content
For this trick, you need to add a negative bottom margin to the shadow of the top and a negative top margin to the shadow of the bottom.
With that, you should be able to place your shadows correctly and give them the design you want.
Activating the Shadow
To compute if your component must show the top shadow, the bottom one, or both at the same time, we re-used the technic of Marius because it was working super well (kudos to you).
You listen to the scroll of your component and handle bit by the "onScrollHandler" function that saves the last scroll position and information about the scrollbar.
As it sets values via "useState", the component is being rendered, so the "getVisibleSides()" function is triggered again and says if yes or not, you have to show the top and bottom shadow.
That’s pretty much it.
But as I told you earlier, this won’t update the shadow visibility if your content height updates.
Fixing the Shadow if Content Evolves
The logic here is simple when the content height evolved, the height of our wrapper evolved. Still, no scroll events were triggered, so we are not recomputing anything, and the shadow stays in the state it was, even though we potentially don’t need it anymore.
We can easily fix that by resetting the values to the current one every time its height evolves.
This time, we can’t get the component through "event.currentTarget" because there is no event. This is why we have to use a ref.
At Qovery, we love building our new interface in public. Our repository is open-source. You may then access our implementation and see the full source code here. You can also see how we implemented the unit tests for this not-quite-conventional thing to test.
We hope it will help you to reproduce this kind of neat effect on your product, and if many of you request it in the issues of our repository, we will maybe make an npm package for this component so that all of you can enjoy it even more efficiently.
Share on :
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
MCP Server is the future of your team's incident’s response
Learn how to use the Model Context Protocol (MCP) to transform static runbooks into intelligent, real-time investigation tools for Kubernetes and cert-manager.
Romain Gérard
Staff Software Engineer
Compliance
Developer Experience
minutes
March 27, 2026
Beyond the spreadsheet: Using GitOps to generate DORA-compliant audit trails.
In the 2026 regulatory landscape, manual audits are a liability. This guide explores using GitOps to generate DORA-compliant audit trails through IaC, drift detection, and automated segregation of duties. Discover how the Qovery management layer turns compliance into an architectural output, reducing manual overhead for CTOs and Senior Engineers.
Mélanie Dallé
Senior Marketing Manager
Kubernetes
7
minutes
March 20, 2026
Day 2 operations: an executive guide to Kubernetes operations and scale
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Mélanie Dallé
Senior Marketing Manager
Kubernetes
8
minutes
March 18, 2026
The 2026 guide to Kubernetes management: master day-2 ops with agentic control
Master Kubernetes management in 2026. Discover how Agentic Automation resolves Day-2 Ops, eliminates configuration drift, and cuts cloud spend on vanilla EKS/GKE/AKS.
Romaric Philogène
CEO & Co-founder
DevOps
Kubernetes
6
minutes
March 18, 2026
Day-0, day-1, and day-2 Kubernetes: defining the phases of fleet management
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
Morgan Perry
Co-founder
Kubernetes
7
minutes
March 15, 2026
Kubernetes multi-cluster: the Day-2 enterprise strategy
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Morgan Perry
Co-founder
Kubernetes
6
minutes
March 13, 2026
Kubernetes observability at scale: cutting the noise in multi-cloud environments
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
Mélanie Dallé
Senior Marketing Manager
Kubernetes
minutes
March 5, 2026
Understanding CrashLoopBackOff: Fixing AI workloads on Kubernetes
Stop fighting CrashLoopBackOff on your AI deployments. Learn why traditional Kubernetes primitives fail large models and GPU workloads, and how to orchestrate AI infrastructure without shadow IT.