QUÉ FOMO!Website for a three-host podcast, with episodes, individual profiles and a game for the live audience

Design and development of the site at Azirgo SAS for the production company La Jungla: visual system built from the brand manual, content structure, technical SEO, measurement and deployment.

QUÉ FOMO! is an unfiltered conversation podcast between three friends, and its content lives on YouTube and Instagram. But a search engine cannot read a video, an Instagram profile does not explain who each host is, and guests, brands and press had no clear door to write through. The show needed a home of its own that felt as loud as the show itself and, at the same time, made every episode stand on its own in search.

• A home page with the show's concept, the three hosts, the three-block format (Qué pasó!, Tema de la semana and La dinámica), what happens off set, frequently asked questions and a closing call to follow the show.
• A hosts section with a profile of their own for Emilia, Gaby and Lili: their role at the table - the one who provokes, the one who reacts and the one who explodes -, their story, traits, social accounts and the topics they know best.
• An episode archive with the latest one featured on top and, for each episode, a page with a long summary, topics, guests, the brands that sponsored the recording and a minute-by-minute breakdown by segment.
• A player that does not load YouTube until someone presses play, and chapters that jump to the exact second of the video without leaving the page.
• Contact with no backend: the form builds the message with name, email, reason (guest, sponsorship, collaboration or press) and the page it came from, and opens WhatsApp with everything already written. A floating WhatsApp button sits on every page.
• The roulette: a game for the audience during recordings, with a 4-digit code inside a QR shown on screen and a wheel each person spins from their own phone, with no server and no database.
• 1200x630 social images for the sections, every host and every episode, plus every favicon, generated by a script from the logo and the photos.

It is a static Astro 7 site. All content comes from two TypeScript data modules - one with the copy, the hosts, the format blocks and the FAQ, and another with the episodes - and it is served from a Docker container running a minimal Node server on Railway, behind Cloudflare.

For recordings with an audience, the site includes a game that runs entirely in the browser and stores nothing about anyone on any server.

• Episodes live in a typed array rather than a CMS: publishing one means adding a block at the top, and /episodios and the episode page generate themselves. The first item in the array is the featured one, so there is nothing else to touch.
• The player does not mount the YouTube iframe until play, and it uses youtube-nocookie. Loading it upfront brought half a megabyte of third-party scripts and their cookies to a page most people open to read the summary; this way the page weighs what the thumbnail weighs.
• The transcript is never published: it is used to write the summary and the chapters, and it stays there. No quotes are invented, no timestamps are refined beyond what the source gives, and the date and duration are copied from the video's own page, never estimated.
• The roulette has no backend on purpose: the code travels inside the QR and the host does the validation, comparing the 4 digits on the phone with the ones on screen. Every slice has the same weight because any weighting would end up written in the site's public code.
• Analytics - GA4 and Clarity - does not fire outside the real domain: on localhost or a local network IP it is cut off, so tests do not sneak in as visits and pollute the metrics.

• Bringing a very loud brand to the web - pink and lime, animated backgrounds, cut-out photos that bleed past the frame - without hurting performance: the backgrounds are library-free GLSL shaders, all motion respects prefers-reduced-motion and the page renders complete without JavaScript.
• Designing a live game that is useless to tamper with even without a server: the security lies in the human step, the draw uses unbiased crypto.getRandomValues and every code expires after two hours, so an old QR seen on Instagram does not win prizes.
• Making the site feel complete from launch day, with only the first episodes out: the hosts, the format and the FAQ carry the weight, and the episode section grows on its own with every new episode.

The site is in production with the home page, the three host profiles, the episode archive and WhatsApp contact. Every new episode goes in as a data block and shows up with its page, its social image, its structured data and its sitemap entry. The roulette is ready for recordings on its direct routes, kept out of the index, while its home page section remains switched off.