I Tapped the Card: What a 60-Word News Story Actually Gives You on Its Own Page

A news card is a promise in miniature. It shows you a headline, a sentence, a number — and it asks you to believe that tapping it will be worth the second it costs. The ShortNews demo's promise is printed right on its homepage: "News in 60 words. Zero noise." Two earlier posts in this series tested that promise from the outside. The first counted the words on the cards and found them shorter than the ceiling — 10 to 24 words where 60 were allowed. The second counted the stories on the homepage and found 27 slots carrying only 15 headlines. Both times I stopped at the homepage, and both times I wrote the same honest caveat: no story page was opened, so nothing was claimed about what a tap delivers. Today I open them. All fifteen headlines, four story pages read end to end, and the answer turns out to be more interesting than either earlier audit suggested — because the story page is not a longer card. It is a different product from the card, sitting underneath it.

First, the tap itself: every card is a door

Start with the most basic question, because it is the one most demos quietly fail: does tapping actually go anywhere? On this demo, yes — every card. The homepage source carries 28 clickable card references pointing at 15 unique article slugs, one for each distinct headline. The featured AI story opens its own page. The Mars video opens its own page. The walking study and the blockbuster sequel, the two stories that never appear on the /latest page, open their own pages too. Nothing on the homepage is a dead card, and nothing I tapped led to the wrong story — each headline's page carries that headline's summary, which is not something you can take for granted on a seeded demo.

There is one wrinkle worth naming, because it matters to how people actually use a site. The cards are not links. They are article elements with click handlers that send the browser to the story address. A mouse click works fine. But the ordinary link behaviours people rely on — right-click to open in a new tab, middle-click, copy link address — do not apply to a card that has no link in it. It is a small thing, and on a phone, where most short-news reading happens, nobody will ever notice. On a desktop it is the kind of friction that makes a reader open the same story twice by accident instead of queuing three tabs to read in order. The fix is one attribute, and the fact that it is missing tells you something about where the demo's attention went: the tap was tested, the link was not.

The other route onto a story page is the BREAKING ticker that runs across the top of every story page — four stories, repeated twice so the loop looks continuous: the earnings story, the championship final, the blood test, and the exoplanet image. Those four are the only stories reachable from a plain link on the homepage, and the blood test is the interesting one of the four, for a reason I will come back to: it has no card on the homepage at all.

The summary box does exactly what it says

Tap any card and the first thing you meet is a box headed "In 60 words", containing the card's own sentence, word for word, with a word-count label underneath it. The AI story's box says 24 words. The earnings story's says 16. The blood test's says 10. The Mars video's says 15. Those labels match the counts from the first audit in this series, and the match matters: the summary on the story page is not a second draft of the card text. It is the same text, in the same words, with the count printed next to it like a receipt.

That is a small honesty, and it is rarer than it sounds. Plenty of short-form products show you a teaser on the list and a different, longer text on the page, and the gap between the two is where the reader feels tricked. Here there is no gap. What the card promised is what the box contains, and the number under it tells you the promise was kept with room to spare — every summary I opened sits far under the 60-word ceiling. If anything, the box is almost too honest: a 10-word summary labelled as being "in 60 words" reads less like a format and more like a format with most of its space unused. But a reader who came for the short version gets the short version first, before anything else on the page asks for their time, and that ordering is the whole idea working as designed.

Then the page keeps going: the article underneath

Here is the part the card never mentions. Scroll past the summary box and there is a full article. The earnings story carries an "In this story" section: an opening paragraph (revenue of $45 billion against $42 billion expected), a subhead on cloud growth (up 31%), a subhead on the market reaction (shares up 12%, $180 billion added) — about 50 words of body in total. The AI story goes further: about 150 words across five sections, with its own subheads, including the two numbers that carry the piece — 65% of Fortune 500 companies having piloted generative AI in at least one department, and consumer AI apps past 100 million weekly users. The blood test story runs about 70 words in three plain paragraphs with no subheads at all. The Mars story is the shortest body of the four, about 27 words in two paragraphs, because its real content is the video.

So the 60-word promise turns out to be the summary, not the page. The page gives you both: the sixty-words-or-less version up top for the reader in a hurry, and a short article underneath for the reader who wants one more paragraph. That is a better deal than the card advertises, and it is also a slightly muddled one. A reader who wanted only sixty words has to scroll past an article they did not ask for; a reader who wanted the full story gets fifty to a hundred and fifty words, which is a briefing, not reporting. The demo never says which reader it is for, and the page serves both halfway. My own reading: the two-layer page is the right shape, and the layers need labelling — a visible "the short version ends here" would let the hurried reader stop with a clear conscience, and the curious reader keep going without feeling they were promised brevity and handed length.

The video card's punchline

The Mars card says "Watch: Mars Mission Shares Stunning New Footage" and its summary says "Watch the full video breakdown." So I watched — or rather, I checked what the page embeds. The story page carries a YouTube embed, and the video ID in the page source is dQw4w9WgXcQ. That is the same ID behind the card's own thumbnail image, and it is the ID of a video most of the internet recognises on sight: Rick Astley's "Never Gonna Give You Up". The demo's Mars footage is a rickroll.

I should be careful about what this proves. It proves the demo's video slot is wired to a placeholder, not to Mars footage — which is exactly what a demo placeholder is for. Nobody seeded a news demo with real NASA footage; they grabbed the most famous video ID on the platform and moved on. It does not prove the script cannot embed a real video, because the embed itself works: the player frame is there, the video loads, the format does what it is supposed to do. What it does prove is something narrower and more useful: on a demo, never trust a thumbnail. The card's image is a YouTube thumbnail for that same video, so the whole Mars story — card image, summary, embedded player — is one borrowed asset repeated three ways, and a visitor who presses play gets a joke instead of a rover. For a buyer evaluating the demo, the video feature is proven working and the video content is proven fake, and those are two different verdicts that should not be collapsed into one. For a reader, it is a reminder that the demo's polish is stagecraft: real plumbing, borrowed scenery.

The furniture around the story

A story page is more than its article, and this is where the demo shows its fullest hand. Every page I opened carries the same furniture, and most of it is the kind of thing a short-news reader actually uses. "Share this story" sits near the top. Font-size controls (A- and A+) let a reader shrink or grow the text — a small accessibility touch that most news templates skip. "Report this story" opens a form with real categories: Misinformation, Spam, Harassment, Hate speech, Violence, Other. The author gets a bio — Sarah Mitchell is a "Senior tech correspondent with 8 years covering Silicon Valley" — plus a "More by Sarah Mitchell" link. Previous and Next story navigation sits at the bottom. Comments exist, with a counter and a box: "Comments (0)" and "Be the first to comment." The page closes with the newsletter pitch: "Liked this summary? Get 5 top stories in 60 words each, every morning."

Two numbers sit at the top of each page next to the date, and they deserve a sceptical look. The reads counts are 1,302 for the AI story, 3,416 for earnings, 19,872 for the blood test, and 893 for Mars. Those are the demo's own seeded labels, not traffic I measured, and the spread is odd in a way that tells you they were typed in rather than earned: the blood test, published Oct 14, has fifteen times the reads of the featured AI story published Oct 19. Maybe the seeder wanted one big number on the page. Maybe it is random. Either way, a reader should not treat those counts as evidence of what people actually read, and an operator launching on this script should know the counts start as fiction until real readers replace them.

One more piece of furniture is invisible until you read the page source: a sticky anchor ad slot, a 728-pixel leaderboard container fixed to the bottom of the viewport, hidden until an ad fills it. It is the demo's monetisation seam, sitting quietly in the code. A reader will never see it until an ad network does, and an operator should know it is there — it is the difference between a demo that reads clean and a live site that will carry a bottom banner on every story page.

Related stories: the catalogue is deeper than the homepage

Scroll to the bottom of any story page and the demo quietly corrects the impression its homepage gives. Each page shows three related stories from the same category, and some of those stories appear nowhere on the homepage. The earnings page offers "Small Business Optimism Hits Three-Year High" and "Electric Vehicle Sales Jump 35% as New Models Hit Showrooms". The blood test page offers "New Sleep Research Reveals the Ideal Bedtime Window" and "Mediterranean Diet Named Best Overall Diet for Seventh Year Running". Four stories, all real pages, none of them on the homepage's 27 slots.

That changes the maths from the earlier audits. The homepage carries 15 distinct stories; the /latest page lists 14; but the related rails add at least four more, so the demo's catalogue is at least 19 stories deep, and possibly deeper — I only opened four story pages, and each one could be hiding more. The homepage, in other words, is a shop window, not an inventory. A reader who judges the site by its front page alone will conclude it holds fifteen stories. A reader who taps through will keep finding more, one related rail at a time. That is good design accidentally doing the job of a catalogue page: the related rail is the only discovery mechanism that works, because the category pages and the /latest page between them still miss stories the rails surface. The operator lesson is the reverse: if your catalogue is deeper than your homepage, do not make readers excavate it three taps at a time. A real archive page would do in one click what the rails do in four.

The story with no homepage slot

The blood test story deserves its own section, because it breaks the pattern in two directions at once. It has no card on the homepage — not in the featured slot, not in the grid, not in the closing list. The only ways onto it are the BREAKING ticker and the related rails of other health stories. And yet it is, by the demo's own numbers, the most-read story on the site: 19,872 reads, against 3,416 for earnings and 1,302 for the featured AI story. Its summary is the shortest of the four I opened — ten words: "A single blood draw could transform how we catch cancer." Its body is three paragraphs, about seventy words, with no subheads, and it carries the demo's only attribution line: "Originally reported by ShortNews Demo."

Read those facts together and they do not add up to a story the demo is proud of. The most-read story is the one the homepage hides, the shortest summary belongs to the longest-read page, and the only attribution line in the four pages I opened sits on the story nobody is shown. The likeliest explanation is boring: the seeder wrote the blood test as a ticker item and a related item, gave it a big reads number, and never promoted it to a card. But the reader's experience does not care about the explanation. A reader who only scrolls the homepage will never meet the story the demo itself says is its most popular, and a reader who only reads the ticker will meet it as a scrolling headline with no card to hold it. It is the clearest single example in this demo of a gap between what a site contains and what it shows — and it is a gap no visitor can see without tapping.

What the tap doesn't give you

Honesty requires the other half of the ledger, and the story pages have a thin half. I found no source links on the four pages I read — no link to a study, a filing, a press release, or a wire report behind any of the claims, including the earnings numbers and the 65% Fortune 500 figure. The blood test's "Originally reported by ShortNews Demo" line is the closest thing to a source on any page, and it points at the demo itself. A sixty-word summary does not need footnotes; a page that also carries a full article with named numbers does, or at least benefits from them, and a reader who wants to check the 65% claim has nowhere to go from the page.

The dates are the second gap, and they are the same gap the earlier audits found: every story on the demo is dated Oct 13–19, 2026, while the homepage promises summaries "updated every few minutes". The story pages do carry "Updated" timestamps — Oct 20 for the AI and earnings stories, Oct 18 for the blood test — which is a nice touch, a sign that the template tracks updates at all. But updated timestamps on a frozen catalogue are still frozen. Nothing I opened was from today, and nothing on any page proves the site updates, because a demo cannot prove that. Freshness, like breadth, is something a visitor has to take on trust until a live site demonstrates it.

The verdict, in two parts

For a reader, the tap is worth it, and that is not the verdict I expected when I started. The summary box keeps its promise exactly, the article underneath gives you a real second layer instead of a longer teaser, and the related rails keep surfacing stories the homepage never shows. The Mars video is a joke placeholder, the reads counts are fiction, and the sources are absent — but none of those break the core transaction, which is: tap a card, get the news in under a minute, and find more news underneath. If you read short news the way it is meant to be read — a minute in the morning, a minute at lunch — the story page serves you better than the card does, because the card is the advertisement and the page is the product.

For an operator, the story page is the strongest part of this demo, and the fixes are cheap. Make the cards real links so a reader can open three stories in three tabs. Swap the placeholder video for real footage or a clearly labelled placeholder before any buyer watches it. Put a source link under any number the article asserts. Give the catalogue an archive page, because the related rails are currently doing a job a single page should do. And promote the blood test — or whatever your most-read story is — onto the homepage, because a homepage that hides its most popular story is a shop window hiding its best product. None of those fixes needs a new feature. They are all one line of logic, one link, or one editorial decision each, and together they would turn a demo that reads well into a site that behaves well.

Frequently asked questions

Is the 60-word summary the whole story? No. Every story page has two layers: an "In 60 words" box with the card's exact text and a word-count label (10 to 24 words on the pages I opened), and a full article underneath it — about 50 words for the earnings story, about 70 for the blood test, about 150 for the AI story. The 60-word promise is the summary, not the page.

Does every card on the homepage open a story page? Yes. The homepage source carries 28 clickable card references pointing at 15 unique article slugs, one per distinct headline. The cards use click handlers rather than links, so right-click to open in a new tab does not work, but an ordinary tap or click opens the right story every time.

What happens when you tap the Mars video card? The story page embeds a YouTube video, but the video ID in the page source (dQw4w9WgXcQ) is the Rick Astley video — a placeholder, not Mars footage. The embed itself works; the content is borrowed. The card's thumbnail comes from the same video ID.

How many stories does the demo actually hold? More than the homepage shows. The homepage carries 15 distinct stories and /latest lists 14, but the related-story rails on the pages I opened surfaced four more — small-business optimism, EV sales, sleep research, and the Mediterranean diet — so the catalogue is at least 19 stories deep.

Why does the blood test story have 19,872 reads but no homepage card? That is the demo's own seeded number, quoted as its label rather than measured traffic, and the story is reachable only from the BREAKING ticker and related rails. It looks like a seeding choice rather than an editorial one — but it means the homepage hides the story the demo itself calls its most-read.

Is ShortNews a real product I can buy? ShortNews is a short-news website script with a live demo at shortnews-demo.codester.shop. No price is stated in this article because the shop's front page carried no ShortNews listing when checked today — check the shop itself before assuming a price.

How is this different from the earlier ShortNews posts in this series? The first post counted words on the cards; the second counted stories on the homepage. This post opens the story pages — the summary box, the article underneath, the video embed, the related rails, and the page furniture — and asks what the tap itself delivers. Different test, different question, same demo.

Who should not run a short-news site

If your stories need sources, do not launch a format that gives the reader nowhere to check a claim — either add a source link under every asserted number or pick a format with room for one. If your catalogue is small, do not build a homepage of four sections pulling from the same pool and a related rail that knows more stories than the homepage does; either seed deeper first or let the homepage show everything you have. And if your most-read story is not on your homepage, fix that before you fix anything else, because your homepage is the one page every visitor sees, and it should show your best work, not hide it.

Tap the card. The summary is honest, the article underneath is real, and the catalogue is deeper than the window. Just don't press play on the Mars video unless you want to get rickrolled.

---

Earlier in this series: Count the Words Before You Trust the News: A 60-Word Test of ShortNews — the word-count audit of the same demo. And Half the Homepage Is the Same Story Twice: A Repeat Audit of ShortNews — the duplication audit. The most recent script post: The Doctor's Side of the Booking: One Doctor's Working Day Inside DocBook. The blog index carries the full series, and the tool this site is built around is free to use.