All websites

07 / Case study

Piotr Kalewski / 2026

Piotr Kalewski — YouTube videos that reach the site on their own

The Oglądam (“Watching”) page on kalewski.com loads videos straight from the YouTube channel through the YouTube Data API. New videos show up on their own, with a hover preview and a player on the page.

Role
YouTube integration
Year
2026
Scope
  • YouTube Data API
  • Video list
  • Hover preview
  • Modal player
  • JavaScript
Disciplines
  • Webflow
  • YouTube Data API
  • JavaScript
Visit site
The kalewski.com home page: “I design events after which you can measure what changed”

The brief

Piotr Kalewski publishes conversations and recordings about B2B event marketing on YouTube. The Oglądam (“Watching”) page of the Webflow site was to show these videos without copying every new episode into the CMS.

I built an integration with the YouTube Data API. A script on the page fetches the videos straight from the channel, and each one gets a hover preview and a player in a window on the page.

Diagram: the kalewski.com/ogladam page asks the YouTube Data API for videos with a key that works only from that domain, and the API reads the @kalewski channel and sends back the videos with their view counts
A video is published once, on YouTube. The site fetches it on its own.

The list of videos

The script asks the API for every video on the channel, then for the details of each: title, date, thumbnail, duration and view count. Shorts (up to 60 seconds), live streams and private or deleted videos stay off the list. The rest are ordered from the most watched.

The “Materiały Video” page on kalewski.com: a grid of the channel’s videos with thumbnails, titles and publishing dates
The channel’s videos, most watched first.

A new video published on the channel shows up on the site by itself, on the next visit. The thumbnail is always the highest quality YouTube offers for that video.

A preview on hover

Hovering over a thumbnail starts the video playing inside it, muted. The players load before a card scrolls into view, so the preview starts at once. Cards far from the view close their players, so the page never holds all of them at once.

Three video cards; in the middle one a muted video plays in place of the thumbnail
The preview plays in the thumbnail, muted.

A player on the page

A click opens the video in a window on the page, with sound, from the second the preview had reached. The window closes with Esc, the close button or a click beside it, and the video stops playing.

A window with the YouTube player open over the grid of videos, with a close button
The video in a window, from where the preview was.

No server of its own

The integration runs entirely in the page’s code in Webflow, with no server to maintain. That is why the YouTube Data API key is visible in the code. It gives no access to the account: it only reads what is public on the channel anyway, and Google accepts it from kalewski.com only.

The result

Piotr Kalewski publishes videos on YouTube only, and the Oglądam page shows them by itself, with no developer and nothing entered in Webflow. Interviews and recordings made outside the channel have a section of their own in the Webflow CMS.

Questions

  • Do new videos have to be added in Webflow?

    No. A video published on the YouTube channel shows up on the site by itself. Webflow keeps only the look of the grid and of the player window.

  • Is an API key visible in the page’s code safe?

    The key gives no access to the YouTube account: it only reads what is public on the channel anyway. Google accepts it from kalewski.com only.

Tell me what you need.

Reply within 24 h

What is it about?

Please enter your name.

Please enter a valid email address.

Please write a message (min. 10 characters).

Add details: company, timeline, budget
Budget optional

Form data is used only to reply to your message. Privacy policy

SR / Terminal

Tab completes · ↑↓ history · Esc closes