I replaced my homepage feature list with a 3-step guide: copy link, paste, download
The homepage of ramrom.io used to open with a feature list. A tidy row of bullets: no sign-up, no watermark, works on every platform, free forever. It read well, it said nothing, and it did not help anyone download a vid
The homepage of ramrom.io used to open with a feature list. A tidy row of bullets: no sign-up, no watermark, works on every platform, free forever. It read well, it said nothing, and it did not help anyone download a video.
I replaced it with three steps, each with a small picture: copy the link, paste it here, download. That was the whole change, and it was the best copy decision I have made on the site so far.
The problem with a feature list
A feature list describes the tool. A visitor does not arrive wanting a description; they arrive with a link in their clipboard and one question: how do I get this video onto my phone? Every line of a feature list is an answer to a question nobody asked. "No watermark" is only interesting after you already trust the tool. "Works on TikTok, Instagram and Facebook" is only interesting if you are choosing between tools, and most visitors are not — they clicked a search result and want to get on with it.
Worse, the list pushed the actual tool down the page. On a phone, which is where most of my visitors are, the link box was below the fold. People had to scroll past my sales pitch to reach the thing they came for. That is backwards.
Three steps, nothing else
The replacement is a short horizontal strip above the link box. Step one: copy the video link from the app. Step two: paste it in the box below. Step three: pick a quality and tap download. Each step has a number, a short line of text and a small illustration — a phone with a link being copied, a box with a link landing in it, a file coming down with an arrow.
I drew the illustrations as simple inline SVG, not photos and not stock art. Three reasons. First, they add almost nothing to the page weight; the whole homepage stays under 100KB. Second, they cannot fail to load the way a hotlinked image can. Third, they look the same on every screen because they scale. A tool page should not carry decorative images that cost a visitor data on a slow connection.
The steps are not clickable and they do not do anything clever. They are there to answer the one question a new visitor has: what do I do here? Once you have read them, you already know. The link box is right underneath, so the answer and the action are in the same glance.
What changed in the code
Almost nothing. The old feature list was a <ul> with six items. The new guide is three <div> blocks in a flex row that wraps into a column on narrow screens, with a big number styled in CSS and a short line of text under each one. No JavaScript at all. That matters more than it sounds: the guide works before any script loads, it works with JavaScript switched off, and it cannot break when I change the shared JS engine that powers the eight tool pages.
I also kept the wording brutally plain. "Copy the link" instead of "Copy the URL of your desired media". "Paste it here" instead of "Paste the copied link into the input field above". If a line needs more than seven words, it is the wrong line. The visitor is not reading for pleasure; they are scanning for the next thing to do.
The lesson I keep relearning
Every time I write copy for this site, I am tempted to explain what the tool is. Every time, the version that wins is the one that explains what to do. A downloader is not interesting. Downloading a video is. The feature list was about the tool; the three steps are about the visitor.
The same thinking now guides every new page I add. Before I write a paragraph about a feature, I ask whether the visitor would rather have a step. Most of the time, they would.
If you are building a single-purpose tool, try it: delete your feature list, write down the three things a visitor actually does, and put those at the top. You will find the page gets shorter, the tool gets closer to the top, and nobody misses the bullets.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.