A video-oriented website does not need to place every video in the same card and location. After revising K-POP PULSE’s entrance, a request asked whether shorts could appear there too. Later questions concerned an apparently small video selection and material from other appearances.
I distinguish the implemented short-video list from the additional browsing ideas. Expanding source material, turning it into articles and making it findable are different tasks. This story does not claim a new test of every external player’s current playback behavior.
Material can remain findable without becoming an article
The operating records do not treat every brief upload as another news article. Collected material and material worth an editorial explanation are different decisions. A video shelf offers a route separate from article publication. A title and player alone do not require the same editorial unit.
Another site can assign different responsibilities to a case video, a brief use scene, a long explanation and an announcement. I would define what visitors need to find and understand before choosing by file type. Expanding a video list and publishing news should not be evaluated as one count.
The initial list used URL and display conditions
The July 30 query reads recent stored items with a shorts path, excludes duplicate URLs and limits displayed items. Following a report that playback was unavailable, a later edit adds an embed-verification state to that selection. The initial and revised conditions are separate historical states.
This establishes how that list was assembled at the time, not the present classification of every short video or a platform-wide duration rule. Keeping URL-shape classification separate from recorded embed status identifies what needs another check when adapting the approach.
Vertical cards were browsed along a horizontal shelf
The historical CSS places portrait cards on a horizontal shelf. JavaScript replaces a chosen thumbnail with an embed and handles Enter and Space input. These are evidence of intended code behavior, kept separate from a fresh observation of playback on every device.
Aspect ratio is only part of the question. Inspect which title and subject lead to selection, how someone returns to an unplayed item, and where keyboard or touch input moves. The early wheel-to-horizontal conversion also needs evaluation against document scrolling during integration.
An apparently small list does not establish a small collection
The initial implementation distinguishes candidate retrieval from the visible limit. A historical output of ten cards describes that shelf, not the whole collection. Category, embed state, deduplication, ordering and a display limit can each affect the result.
The request for other appearances should not be rewritten as a completed feature either. It raised questions about source identity, connection to the subject and separation from the official list. Before increasing collection to address a sparse display, compare those conditions with the material already retained.
Continue the test from discovery into playback
A shorts area has been observed on the public homepage. Every selection, audio choice and player transition has not been freshly executed in this review. A long video read through an article and a short video selected from a shelf may share a subject while following different screen flows.
During integration, follow reading the title, choosing the card, playing it and reaching another item. Inspect a route after failure, the position on return and duplicate appearances. Recording what the path resolves is more useful for reuse than describing only how many videos appear.
Keep the eligible-item count with the displayed count when diagnosing a sparse shelf. A limit, a failed eligibility condition and missing source material call for different follow-up work.