Ma77Ball opened a new pull request, #84:
URL: https://github.com/apache/incubator-texera-site/pull/84

   ### What changes were proposed in this PR?
   - Replaces the YouTube `<iframe>` embeds on the Videos page with clickable 
cards that link out to each clip on YouTube, because Apache's site-wide 
Content-Security-Policy blocks third-party iframes (its `frame-src` allows only 
`'self'` plus apache domains).
   - Serves each video's thumbnail locally from `static/images/videos/` with 
descriptive, kebab-case filenames, so images load from `'self'` and are not 
blocked by the CSP (which also restricts remote images).
   - Restyles each card with a YouTube-style red play badge and a more 
prominent box (stronger border and deeper shadow).
   - Documents the thumbnail workflow and adds an optional `thumb:` field in 
`data/videos.yaml`.
   ### Any related issues, documentation, discussions?
   Follow-up to #83, which added the Videos page; on staging the iframe embeds 
were blocked by the Apache CSP.
   ### How was this PR tested?
   - Run `hugo --gc` from the repo root, expect a clean build with no errors.
   - Open `/videos/`, confirm each card shows a local thumbnail with a red play 
badge and there is no blocked or empty iframe.
   - Click a card, confirm it opens the correct 
`https://www.youtube.com/watch?v=...` page in a new tab.
   - Type in the search box, confirm cards filter live by title and description.
   - CSP check: no third-party iframe or image requests remain, so nothing is 
blocked. This can only be fully confirmed on the deployed `*.apache.org` 
staging site (where the CSP header is applied), not on a local build.
   ### Was this PR authored or co-authored using generative AI tooling?
   Co-authored with Claude Opus 4.8 in compliance with ASF.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to