Tackle City | Supplier Content Hub POC

What this POC proves, and what it surfaced

Ingestion works with no API key. Every item below came from youtube.com/feeds/videos.xml?channel_id=UC7l_C-SB-TyxXR3qmgBnWPw, the free per-channel RSS feed. It returns id, title, description, thumbnail, published date, view count and rating. That is everything a card needs. The YouTube Data API is not required for v1, which removes the quota constraint.
Playback is the standard embed. Click any thumbnail: it swaps to a youtube-nocookie.com iframe. Nothing is rehosted, the view still counts for Fox, and we stay the right side of copyright.
Discipline is a channel property, not a video property. The channel is "Fox International Carp Fishing", so every video is carp. Fox Rage (predator) is a separate channel. So we set discipline per feed at source and only refine per video. That is cheaper and far more reliable than classifying every item.
Shorts are the real content problem. 10 of 15 items are Shorts, and most are promo noise ("Kiss the camera Moz!"). But one, "60 Seconds to tie a Solid Bag", is a genuine tutorial on 86,860 views. So we cannot filter Shorts out wholesale by format. This is exactly why the staff review queue is a Must, not a Should. Toggle "Hide promo shorts" to see the difference.
Product launch videos are the deep-link goldmine. The two launch films list products with timestamps in the description (Tuff Skin Hooklinks, Horizon Throwing Stick, EOS FD Reels, Spomb XD Shockleader). These map cleanly onto catalogue products and are the strongest content-to-order path in the set.

Reading the POC

Category rail is the primary navigation, per the agreed IA. With one carp channel loaded, Predator and Sea show as empty states, which is honest rather than hidden.
Tags use the governed taxonomy (Technique:Zig-Fishing, Category:Terminal-Tackle) so content and catalogue share one vocabulary.
"Shop the kit" is illustrative. Real deep-links resolve against in-stock published products.
Data is baked in as a static snapshot. In production a scheduled Cloudflare Worker polls the feeds and writes content_item rows to Supabase (browsers cannot fetch YouTube RSS directly, CORS).