Website design and build guide
Build a website people want to scroll
Start with the visitor’s journey. Decide what they need to see on the first screen and what they should be able to do at the end. Give every scene a job along that path.
Download the Arabic PDF- 1Detail
- 2Process
- 3Reveal
- 4Next step
Try a scroll-driven scene
Scroll inside the scene or choose a stage. Scroll back to see the motion reverse.
Storyboard the visitor’s journey
Write the task in one sentence. The visitor should understand the offer, see the result, and know where to go next.
- Opening
- Lead with the result or one specific detail. Keep the heading and action visible on the first screen.
- Process
- Show one detail that explains what makes the result valuable.
- Reveal
- Give the finished result room to register before the next scene.
- Next step
- Offer a product category, a contact option, or another useful action. Keep it reachable directly from navigation.
Sketch four boxes. For each one, write what the visitor sees, learns, and can do.
Map the motion to scrolling
Give each scene a start and end. A small movement may be enough to guide the eye.
- Start
- Present a useful still image and keep the text in the page.
- Scroll
- Map progress through the scene to a number from zero to one so the motion reverses as the visitor scrolls back.
- End
- Hold the reveal briefly, then return the visitor to reading and navigation.
- Reverse
- Try fast scrolling, stopping halfway, and scrolling backwards. The scene should follow the current position.
Start with one moving layer. Add complexity once the first scene reads clearly on a phone.
Build the first scene
Create a regular readable page first. Add a scene containing an image and use scroll progress to move that layer.
- Readable content
- Use real headings, copy and links. Give meaningful images descriptive alternatives.
- Small animation
- Read the scene position and update one transform per animation frame.
- Optional pinning
- Pin the image on larger screens if it helps the story. Let it flow naturally on narrow and short screens.
<section data-scene>
<h2>Scene heading</h2>
<img data-layer src="scene.webp" alt="Describe the scene">
</section>
<script>
const scene = document.querySelector("[data-scene]");
const layer = scene?.querySelector("[data-layer]");
const reduced = matchMedia("(prefers-reduced-motion: reduce)");
let frame = 0;
function render() {
frame = 0;
const box = scene.getBoundingClientRect();
const start = innerHeight * 0.75;
const p = Math.min(1, Math.max(0, (start - box.top) / box.height));
layer.style.transform = reduced.matches ? "" :
"translateY(" + (1 - p) * 24 + "px)";
}
if (layer) {
const update = () => { if (!frame) frame = requestAnimationFrame(render); };
addEventListener("scroll", update, { passive: true });
addEventListener("resize", update);
reduced.addEventListener("change", update);
update();
}
</script>The sample moves one layer. Test it before tying a large image sequence or video to scrolling.
Keep the first screen light
Start with a compact still image. Load heavier media near the relevant scene or when the visitor requests it.
- Opening image
- Reserve its dimensions. Use a crop and size that fit phones.
- Later media
- Defer distant scenes. Test a smaller frame sequence or a lighter video before loading everything.
- Short screens
- Reduce pinning time. Test thumb navigation, larger text and short landscape layouts.
- Reading mode
- Honor the visitor’s reduced-motion preference. Keep the same information, links and stills available without motion.
Test on a real phone and a slower network. A development machine covers only part of the experience.
Test the journey before release
Measure whether people can complete their task from opening to action.
- Core path
- Follow the product, directions or contact link using touch and the keyboard, then navigate back.
- Scroll behavior
- Test downward, backwards and fast scrolling. Look for jumps, media failures and sections that trap the visitor.
- Load and stability
- Record the largest element’s load time, initial media bytes and unexpected layout shifts. Compare versions under identical conditions.
- Visitor action
- Track reach to the reveal and clicks on the next action. Compare click sessions divided by visit sessions using the same time window and measurement rules.
In one local sample at 390 pixels wide and 1.6 Mbps, the largest element appeared in 2.42 seconds and 2.46 MB loaded over approximately 22 seconds. Use the same test conditions when comparing your own versions.
A worksheet for your first build
Start with one page and one scene that takes visitors from a detail to a result.
- Fill in the blanks
- The visitor comes for ____. They first see ____. The reveal shows ____. Next they can ____.
- Build prompt
- Fit my content into four scenes. Give each a short heading, an image and one movement. Keep links usable with motion on and off, and test phone and desktop layouts.
- Definition of done
- The text reads on a small screen, the action works, reverse scrolling feels natural, and the static page communicates the same information.
Show the first scene to someone new to the project. Ask what they understood and where they would click next.