Your task is to build the actual MVP website now for Christina Korf / “International Love Story.” Do not stop at planning. Do not only describe what you would do. Perform the work: 1. first harvest as much real content as possible from the provided links 2. normalize and save that content into structured local data files 3. then build the actual site using the harvested content first and placeholders only where necessary This is a build task, not a brainstorming task. ================================ HARD RESET / NO REUSE ================================ This run must be treated as a full rebuild from scratch. Do not preserve, reuse, defend, or lightly tweak any previous International Love Story MVP, prototype, preview, placeholder build, harvested data, or prior assumptions. If any previous International Love Story implementation exists, treat it as stale and disposable. Remove the old implementation artifacts first, then rebuild cleanly from zero. Specifically: - do not treat any existing `demo-site` files as authoritative - do not keep old harvested JSON just because it already exists - do not report "already aligned" or "already consistent with the brief" as a substitute for rebuilding - do not use previous failure states as justification for shallow placeholders - if an old preview route exists, do not assume it is acceptable without rebuilding and re-validating the underlying content The goal here is not to preserve the previous MVP. The goal is to replace it with a materially better build created from a fresh harvest pass. ================================ NETWORK ACCESS / EXIT NODE ================================ For this run, you should assume richer source access is required than in the previous attempt. The server has access to a Tailscale exit node on my Pixel 6a, and you must explicitly prefer using that connectivity path when scraping or validating sources that were previously blocked, rate-limited, geo-sensitive, or inconsistently accessible. Treat the Pixel 6a exit node as part of the intended execution context for this task, not as an optional afterthought. If source access looks restricted, do not immediately fall back to placeholders. First: 1. verify that the Pixel 6a Tailscale exit node path is active / available 2. retry the blocked or partial source fetches using that network path 3. only after that, document what still remains inaccessible You should make a real second attempt to harvest more source material before accepting any placeholder gaps. ================================ PROJECT CONTEXT ================================ This is a brand-new public-facing MVP website. There may have been an older or unpublished website with limited information, but for implementation purposes treat this as a new build. The site must be: - mobile-first - conversion-oriented - warm, intimate, feminine, and editorial in tone - structured as a static MVP first - ready for later evolution into a CMS-backed content system The site should function as both: - a brand / trust-building site - a lead generation and conversion funnel - a story-driven discovery experience centered on the podcast - a community growth surface You should make pragmatic decisions and ship a cohesive result even if some source content is incomplete. ================================ PHASE 1: CONTENT HARVEST FIRST ================================ Before building anything, do a content-harvest pass from the provided links. Do not jump directly into design or implementation until you have extracted and organized as much real-world information as possible. -------------------------------- SOURCE LINKS -------------------------------- Community: https://chat.whatsapp.com/Kf9cT6PLNulK0M2V5zrAIk?mode=ac_t&utm_source=ig&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGnenyiY69ffx1B_PQ9CheGAF5nsu4fYGs96Go0jsUQtUfEJvN-fa1Gro2QH9s_aem_7ZehaYv5ZuwWbpdgzbKQag Lead magnet: https://shop.beacons.ai/internationallovestory/6f41bb13-efe6-42c7-a6ea-cfd48964a1aa?utm_source=ig&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGn_PM6hovSY2_c7XBlBNDBmn4j7fzGJPZknWS2mbwkv-fX4ocX1EFYxOaOmoc_aem_MpRBkePpHwtTGIgyTKmJFg Podcast / platform hub: https://linktr.ee/internationallovestory?utm_source=linktree_profile_share<sid=298e35a1-a979-4a08-8f55-f490940a6f3d&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGnIRpmzkcCYAWHwoKsBIt48g5yuPb-7JIB0nVrf0LIaodwK0jwsW_eaTl3ACI_aem_8BeYgYkhgvXKtOcPVKETNg Instagram: https://www.instagram.com/internationallovestory/ -------------------------------- HARVEST OBJECTIVE -------------------------------- Extract every usable piece of real source material you can from these URLs and any immediately linked public pages they expose. You are trying to avoid generic placeholder work. Use real CTA targets, real wording, real offer names, real bio language, real platform links, and real visual signals wherever possible. -------------------------------- WHAT TO EXTRACT -------------------------------- 1. CTA destinations Collect: - the exact outbound URLs - likely user-facing CTA labels - category of each CTA: - community - lead magnet - workshop - coaching - podcast - YouTube - Instagram - story submission - newsletter - application - which CTAs appear to be top-priority in the existing funnel 2. Brand copy and positioning Collect: - brand name - person name(s): Christina / Tina / Christina Korf if visible - bios - taglines - short intros - “about” style descriptions - repeated phrases - promise / transformation language - community framing language - how she describes the audience 3. Offer inventory Collect: - the lead magnet title and short description if visible - community offer name and wording - any workshop titles - any coaching offer names - any “tell your love story” / “tell your story” applications - any newsletter or free resource offers - pricing only if it is explicitly public - any short benefit bullets if available 4. Podcast ecosystem Collect: - podcast platform destinations - Apple / Spotify / YouTube links if discoverable - podcast description - visible episode titles if accessible - host description - themes and recurring categories - visible evidence of episode count if available - if exact episode data is not directly accessible, collect enough ecosystem details to inform seed data 5. Visual brand references Collect: - profile images - headshots - podcast cover art - thumbnails - logo if visible - dominant brand colors - styling cues: - elegant - warm - feminine - global / travel-oriented - community-oriented - any recurring iconography or image motifs 6. Social proof and trust signals Collect: - visible audience signals - community count if shown - follower count if shown - testimonials or quotes - featured platforms - phrases indicating credibility, experience, or community presence -------------------------------- HARVEST RULES -------------------------------- - Prefer real extracted content over invented placeholder copy. - If a page is blocked, use accessible previews, metadata, social previews, linked public pages, or search-discoverable public mirrors if available in your environment. - If exact facts are not visible, do not fabricate them. - Where a fact is uncertain, either omit it or mark it as placeholder. - Make conservative inferences only when they are strongly implied by the visible source material. - Preserve the original source URLs in the data layer. - Do not let harvesting become endless. Gather enough to build a strong MVP, then move to implementation. -------------------------------- SAVE HARVEST OUTPUT -------------------------------- Create a local data layer before building. Save extracted information into structured files such as: - data/brand.json - data/ctas.json - data/offers.json - data/podcast.json - data/episodes.json - data/assets.json - data/source-notes.md Minimum expectations for those files: data/brand.json - brandName - personName - shortBio - longBio - audience - positioning - tone - sourceUrls data/ctas.json - primaryCta - secondaryCta - tertiaryCtas[] - each item with: - label - href - type - source - priority data/offers.json - community - leadMagnet - workshops - coaching - storySubmission - each item with: - title - description - href - status - source - placeholder (boolean if needed) data/podcast.json - title - description - platformLinks - sourceHub - notableThemes[] - episodeCountText (if exact number isn’t available, use soft wording only if grounded) data/episodes.json - if real episode list is accessible, store real entries - if not fully accessible, create well-structured seed entries based on known themes and mark them as curated placeholders where necessary data/assets.json - logo - profileImage - coverArt - gallery[] - colorPalette[] - notes data/source-notes.md Document: - which source links were accessible - which were blocked - what was extracted from each - what remains unknown - what was inferred - what is placeholder ================================ PHASE 2: BUILD THE MVP SITE ================================ After the harvest pass, build the actual MVP site. Do not merely describe the ideal site. Implement it in the existing project stack already present in the workspace if one exists. Prefer modifying the existing frontend app rather than creating unnecessary duplicates. If exact assets are missing, use tasteful placeholders and wire the code so real assets can be swapped later. ================================ BUSINESS GOALS (PRIORITY ORDER) ================================ Primary goals: 1. Drive community signups 2. Convert visitors into paid coaching/workshops 3. Collect emails for the free lead magnet 4. Grow podcast listens/views These priorities should shape layout, CTA hierarchy, and copy emphasis. Community is the primary conversion goal. ================================ BRAND / MESSAGE DIRECTION ================================ Brand: - International Love Story Primary figure: - Christina / Tina - position her as the face and guide behind the brand Core audience: - primarily women in intercultural relationships - especially women navigating language barriers, different family systems, migration, loneliness abroad, identity shifts, and communication stress Emotional promise: - “you are not the only one” - real stories, practical tools, and supportive community for women in intercultural love Tone: - warm - intimate - feminine - emotionally intelligent - honest - trusting - globally aware - story-driven Avoid: - corporate startup design - generic coaching clichés - sterile wellness branding - vague empowerment filler - placeholder copy that sounds fake when sharper language can be written ================================ KNOWN CONCEPTUAL CONTENT TO REFLECT ================================ Use these themes and known positioning cues in the content model and copy: - international / intercultural / multicultural relationships - long-distance relationships - communication across languages - culture clash and misunderstandings - moving abroad for love - family expectations - identity and belonging - finding community abroad - women-centered support - real stories from intercultural couples - practical relationship and communication guidance The site should feel like a blend of: - podcast archive - editorial storytelling platform - women’s support community - workshop / coaching funnel - lead magnet funnel ================================ HOMEPAGE INFORMATION ARCHITECTURE ================================ Build the homepage with this flow: 1. HERO SECTION Purpose: - instantly communicate who this is for - establish emotional resonance - drive the primary CTA Requirements: - strong emotional headline for women navigating intercultural love - supportive subheadline explaining what International Love Story is - primary CTA: join the community - secondary CTA: get the free communication guide (or actual lead magnet title if found) - tertiary CTA: listen to the podcast - visually feature Christina/Tina if image assets are available - premium, warm, editorial look - must feel highly intentional on mobile 2. TRUST / SOCIAL PROOF STRIP Purpose: - establish legitimacy quickly Include: - language like: - real stories - intercultural relationship support - practical communication tools - community for women - if supported by harvested data, mention: - 100+ podcast episodes or softer wording like “a growing library of conversations” - keep this concise and scannable 3. SIGNATURE MAP / WORLD DISCOVERY SECTION Purpose: - create the memorable “wow” experience - visually reinforce the global relationship concept Concept: - each episode is represented by two connected points - the connection should evoke a “red thread” / “red string of connection” - the two points can represent: - host / Christina location context - guest / partner / featured story location - for MVP, a polished 2D world map or stylized faux-globe is acceptable if a full globe is overkill - prioritize clarity, beauty, and touch usability over visual gimmicks Requirements: - visible connection lines between two places per story - highlighted pins on tap / click - clear selected state - smooth, lightweight interaction - mobile-friendly layout 4. SEARCH / FILTER DISCOVERY Purpose: - help visitors find relevant stories by emotional relevance first Search and filter priority: 1. themes 2. country names 3. episode titles 4. guest names Requirements: - search input - theme chips / filter pills - country-based discovery - results list tied to map selection - discovery should feel inviting, not like an admin dashboard Theme chips should include: - communication - language barriers - long-distance - family - moving abroad - identity - friendship - paperwork / visas - multilingual children - cultural adjustment 5. EPISODE DETAIL MODAL Purpose: - turn discovery into deeper engagement Trigger: - clicking a map connection - clicking a search result - clicking a featured episode card Modal should include: - episode title - guest name(s) - countries involved - short summary - theme tags - outbound buttons (listen / watch / learn more) - optional secondary CTA into community or lead magnet Rules: - mobile-first modal layout - large tap targets - no embedded players in MVP - outbound links only 6. FEATURED OFFERS / FUNNEL SECTION Purpose: - convert visitors into the core business outcomes Build distinct cards/blocks for: - community - free communication guide / lead magnet - workshops - coaching - “tell your story” / story application Each item should include: - title - short benefit-oriented description - direct CTA button - supporting microcopy Hierarchy: - community first - lead magnet second - workshops/coaching next - story submission as a narrative/community expansion CTA 7. ABOUT CHRISTINA / TINA SECTION Purpose: - humanize the brand and create personal trust Include: - short personal narrative - bridge from lived experience to practical support - position her as relatable, credible, and emotionally grounded - if harvested content gives exact phrasing, use that - otherwise write tasteful copy consistent with the brand 8. PODCAST SECTION Purpose: - highlight the podcast as a major trust and discovery asset Include: - description of what listeners get - platform buttons linking out to real platform destinations - featured or recent episodes - support the brand story without overpowering the main conversion funnel 9. FINAL CTA SECTION Purpose: - end with a clear emotional conversion moment Requirements: - strong closing statement - primary CTA: join the community - secondary CTA: free guide - optional CTA: tell your story ================================ SITE CONTENT REQUIREMENTS ================================ The MVP should include both media and offers: - podcast archive - free communication guide / lead magnet - community for women - workshops / coaching - “tell your story” application All guest names and locations are intended to be public on the map. Outbound links are acceptable and preferred over heavy embeds. ================================ DATA MODEL REQUIREMENTS ================================ Create a structured content layer that powers the UI. At minimum define: - episodes[] - featuredThemes[] - countries[] - offers[] - testimonials[] (real if available, tasteful placeholder if not) - ctas[] - brand metadata Each episode entry should support: - id - title - slug - guestName - guestCountry - hostCountry - connectedCountries[] - themes[] - summary - platformLinks - featuredImage - publishedAt - isFeatured - source - placeholder (boolean if needed) Seed content requirement: - create at least 8 to 12 compelling episode entries - use real episode data if accessible - otherwise create curated structured seed entries aligned with harvested themes and mark uncertain fields clearly - the map must not be empty ================================ DESIGN DIRECTION ================================ The design should feel: - warm - intimate - feminine - editorial - story-driven - globally connected - polished and emotionally resonant Avoid: - default bland startup layouts - overly dark moody luxury aesthetics - generic pastel wellness sameness - flat white pages with random purple gradients Preferred palette direction: - soft cream / ivory backgrounds - terracotta / clay / muted rose accents - deep olive / warm espresso / ink contrast tones Typography: - choose expressive, intentional type - avoid boring default system-only feel - the typography should feel human and premium Background and atmosphere: - use subtle texture, layered gradients, soft glows, shapes, map overlays, or paper-like warmth - create section contrast so the page feels composed, not monotonous Motion: - hero reveal - selected map connection emphasis - modal transitions - staggered content reveals if useful - keep motion tasteful and not distracting ================================ UX RULES ================================ Mobile-first is a hard requirement. The site must work well on small screens: - readable hierarchy - comfortable spacing - clear thumb-friendly buttons - usable filters - modal interactions that don’t feel cramped - no tiny map hit targets A first-time visitor should immediately understand: - who this is for - what International Love Story is - what to click next ================================ COPY DIRECTION ================================ Write copy for women navigating intercultural relationships. Center the emotional realities: - feeling misunderstood across languages and cultures - rebuilding life in a new country - loneliness and missing community - relationship strain caused by distance, migration, or differing norms - wanting practical communication tools - wanting to feel less alone The copy should make visitors feel: - seen - soothed - guided - invited into a real community Do not write: - hollow motivational fluff - vague “empowerment” text - generic coaching copy detached from the intercultural-love niche ================================ TECHNICAL EXECUTION RULES ================================ - Use the existing project/app in the workspace if there is one. - Prefer modifying the existing frontend app instead of creating unnecessary duplicates. - Build the site so it can be previewed immediately. - Use the harvested content as the primary source of truth. - Where data is missing, fill gaps with tasteful placeholders and clearly structured code. - Keep architecture simple and fast to iterate. - If useful, separate data from presentation cleanly so later content updates are easy. ================================ DELIVERABLES ================================ By the end of this task, you should have: 1. A harvested source-data layer - brand, CTAs, offers, podcast metadata, assets, notes 2. A functioning MVP site implementation - homepage and supporting sections - interactive map/discovery concept - modal-based story detail interaction - real CTA destinations wired in 3. Clean structured content - enough seeded/real data to make the experience feel complete 4. A previewable result - not just files, but something that can be run / viewed in the local app stack ================================ DECISION RULES - If a source page blocks access, use the best accessible public metadata or previews you can get. - Prefer shipping a coherent, beautiful, functional prototype over waiting for perfect data. - Make strong product decisions without unnecessary questions. ================================ SUCCESS CRITERIA ================================ The finished result should feel like a real launchable prototype for International Love Story: - emotionally compelling - clearly targeted to women in intercultural relationships - conversion-first - community-forward - story-driven - globally themed - visually distinctive - mobile-first - immediately useful Do the work now. If you want, I can also make: 1. a shorter Telegram-sized version of this same prompt 2. a version explicitly telling Pipo when to delegate pieces to codex, gemini, and deepseek-code 3. a stricter implementation-only version that removes most brand prose and focuses on execution steps › I think I might just send this through the openclaw gateway chat so its not compressed. Yes the idea of having a version that explicitly tells pipo when to delegate the pieces might be ideal tbh. discard your #3 proposal, no problem. discard your #1 proposal, as I will send it via direct chat to pipo • Use this version for Pipo. It keeps the full harvest-then-build workflow, but explicitly tells Pipo when to delegate to sub-agents and what each agent should own. Your task is to build the actual MVP website now for Christina Korf / “International Love Story.” Do not stop at planning. Do not only describe what you would do. Perform the work: 1. first harvest as much real content as possible from the provided links 2. normalize and save that content into structured local data files 3. then build the actual site using the harvested content first and placeholders only where necessary This is a build task, not a brainstorming task. You are the orchestrator. You should stay focused on coordination, decision-making, quality control, and synthesis. You should delegate substantial execution work to specialist sub-agents whenever that will speed up delivery or improve quality. ================================ ORCHESTRATION RULES ================================ You are Pipo, the main coordinating agent. Your job: - own the product direction - own the interpretation of the brief - own the final integration - own quality control - own the final user-facing result You should avoid doing all implementation manually in the main session if specialist agents are available. Use sub-agents strategically: 1. Delegate to `codex` for: - frontend implementation - component creation - data modeling - wiring the interactive map/discovery UI - refactoring existing app structure - building modals, sections, CTA flows - practical coding tasks in the existing project 2. Delegate to `gemini` for: - content harvesting from the supplied links - extracting CTA targets, copy, offer names, platform destinations - synthesizing brand voice from public pages - drafting polished copy blocks from harvested information - identifying structure and narrative opportunities in the source material 3. Delegate to `deepseek-code` for: - alternative implementation ideas - debugging hard UI issues - proposing better component/data architecture - checking edge cases in search/filter/map interaction - suggesting performance or interaction improvements - second-opinion code review on tricky parts Delegation expectations: - delegate early, not only after getting stuck - parallelize where sensible - give each sub-agent a tightly scoped task - bring their outputs back into one coherent build - do not dump the entire project blindly on one sub-agent - preserve momentum: while one agent is harvesting, another can inspect the codebase You remain responsible for: - choosing the final direction - reconciling conflicting recommendations - integrating the work - making sure the final result actually matches the brief ================================ PROJECT CONTEXT ================================ This is a brand-new public-facing MVP website. There may have been an older or unpublished website with limited information, but for implementation purposes treat this as a new build. The site must be: - mobile-first - conversion-oriented - warm, intimate, feminine, and editorial in tone - structured as a static MVP first - ready for later evolution into a CMS-backed content system The site should function as both: - a brand / trust-building site - a lead generation and conversion funnel - a story-driven discovery experience centered on the podcast - a community growth surface You should make pragmatic decisions and ship a cohesive result even if some source content is incomplete. ================================ PHASE 1: CONTENT HARVEST FIRST ================================ Before building anything, do a content-harvest pass from the provided links. Do not jump directly into design or implementation until you have extracted and organized as much real-world information as possible. Recommended delegation: - Send the full harvest task to `gemini` first. - In parallel, send `codex` a codebase inspection task so it can identify the existing frontend app and prepare for implementation. - If harvesting is messy or inconsistent, ask `deepseek-code` for a compact data schema proposal after initial findings are in. -------------------------------- SOURCE LINKS -------------------------------- Community: https://chat.whatsapp.com/Kf9cT6PLNulK0M2V5zrAIk?mode=ac_t&utm_source=ig&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGnenyiY69ffx1B_PQ9CheGAF5nsu4fYGs96Go0jsUQtUfEJvN-fa1Gro2QH9s_aem_7ZehaYv5ZuwWbpdgzbKQag Lead magnet: https://shop.beacons.ai/internationallovestory/6f41bb13-efe6-42c7-a6ea-cfd48964a1aa?utm_source=ig&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGn_PM6hovSY2_c7XBlBNDBmn4j7fzGJPZknWS2mbwkv-fX4ocX1EFYxOaOmoc_aem_MpRBkePpHwtTGIgyTKmJFg Podcast / platform hub: https://linktr.ee/internationallovestory?utm_source=linktree_profile_share<sid=298e35a1-a979-4a08-8f55-f490940a6f3d&utm_medium=social&utm_content=link_in_bio&fbclid=PAZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMjU2MjgxMDQwNTU4AAGnIRpmzkcCYAWHwoKsBIt48g5yuPb-7JIB0nVrf0LIaodwK0jwsW_eaTl3ACI_aem_8BeYgYkhgvXKtOcPVKETNg Instagram: https://www.instagram.com/internationallovestory/ -------------------------------- HARVEST OBJECTIVE -------------------------------- Extract every usable piece of real source material you can from these URLs and any immediately linked public pages they expose. You are trying to avoid generic placeholder work. Use real CTA targets, real wording, real offer names, real bio language, real platform links, and real visual signals wherever possible. -------------------------------- WHAT TO EXTRACT -------------------------------- 1. CTA destinations Collect: - the exact outbound URLs - likely user-facing CTA labels - category of each CTA: - community - lead magnet - workshop - coaching - podcast - YouTube - Instagram - story submission - newsletter - application - which CTAs appear to be top-priority in the existing funnel 2. Brand copy and positioning Collect: - brand name - person name(s): Christina / Tina / Christina Korf if visible - bios - taglines - short intros - “about” style descriptions - repeated phrases - promise / transformation language - community framing language - how she describes the audience 3. Offer inventory Collect: - the lead magnet title and short description if visible - community offer name and wording - any workshop titles - any coaching offer names - any “tell your love story” / “tell your story” applications - any newsletter or free resource offers - pricing only if it is explicitly public - any short benefit bullets if available 4. Podcast ecosystem Collect: - podcast platform destinations - Apple / Spotify / YouTube links if discoverable - podcast description - visible episode titles if accessible - host description - themes and recurring categories - visible evidence of episode count if available - if exact episode data is not directly accessible, collect enough ecosystem details to inform seed data 5. Visual brand references Collect: - profile images - headshots - podcast cover art - thumbnails - logo if visible - dominant brand colors - styling cues: - elegant - warm - feminine - global / travel-oriented - community-oriented - any recurring iconography or image motifs 6. Social proof and trust signals Collect: - visible audience signals - community count if shown - follower count if shown - testimonials or quotes - featured platforms - phrases indicating credibility, experience, or community presence -------------------------------- HARVEST RULES -------------------------------- - Prefer real extracted content over invented placeholder copy. - If a page is blocked, use accessible previews, metadata, social previews, linked public pages, or search-discoverable public mirrors if available in your environment. - If exact facts are not visible, do not fabricate them. - Where a fact is uncertain, either omit it or mark it as placeholder. - Make conservative inferences only when they are strongly implied by the visible source material. - Preserve the original source URLs in the data layer. - Do not let harvesting become endless. Gather enough to build a strong MVP, then move to implementation. -------------------------------- SAVE HARVEST OUTPUT -------------------------------- Create a local data layer before building. Save extracted information into structured files such as: - data/brand.json - data/ctas.json - data/offers.json - data/podcast.json - data/episodes.json - data/assets.json - data/source-notes.md Minimum expectations for those files: data/brand.json - brandName - personName - shortBio - longBio - audience - positioning - tone - sourceUrls data/ctas.json - primaryCta - secondaryCta - tertiaryCtas[] - each item with: - label - href - type - source - priority data/offers.json - community - leadMagnet - workshops - coaching - storySubmission - each item with: - title - description - href - status - source - placeholder (boolean if needed) data/podcast.json - title - description - platformLinks - sourceHub - notableThemes[] - episodeCountText (if exact number isn’t available, use soft wording only if grounded) data/episodes.json - if real episode list is accessible, store real entries - if not fully accessible, create well-structured seed entries based on known themes and mark them as curated placeholders where necessary data/assets.json - logo - profileImage - coverArt - gallery[] - colorPalette[] - notes data/source-notes.md Document: - which source links were accessible - which were blocked - what was extracted from each - what remains unknown - what was inferred - what is placeholder ================================ PHASE 2: BUILD THE MVP SITE ================================ After the harvest pass, build the actual MVP site. Do not merely describe the ideal site. Implement it in the existing project stack already present in the workspace if one exists. Prefer modifying the existing frontend app rather than creating unnecessary duplicates. Recommended delegation: - Give `codex` the main implementation task once the data layer is ready. - Ask `gemini` to draft/refine copy for hero, about, CTA, and offer sections using harvested language. - Ask `deepseek-code` for a focused review of the interaction model and data architecture before final polish. - Have `codex` integrate the accepted copy and structural improvements into the final app. If exact assets are missing, use tasteful placeholders and wire the code so real assets can be swapped later. ================================ BUSINESS GOALS (PRIORITY ORDER) ================================ Primary goals: 1. Drive community signups 2. Convert visitors into paid coaching/workshops 3. Collect emails for the free lead magnet 4. Grow podcast listens/views These priorities should shape layout, CTA hierarchy, and copy emphasis. Community is the primary conversion goal. ================================ BRAND / MESSAGE DIRECTION ================================ Brand: - International Love Story Primary figure: - Christina / Tina - position her as the face and guide behind the brand Core audience: - primarily women in intercultural relationships - especially women navigating language barriers, different family systems, migration, loneliness abroad, identity shifts, and communication stress Emotional promise: - “you are not the only one” - real stories, practical tools, and supportive community for women in intercultural love Tone: - warm - intimate - feminine - emotionally intelligent - honest - trusting - globally aware - story-driven Avoid: - corporate startup design - generic coaching clichés - sterile wellness branding - vague empowerment filler - placeholder copy that sounds fake when sharper language can be written ================================ KNOWN CONCEPTUAL CONTENT TO REFLECT ================================ Use these themes and known positioning cues in the content model and copy: - international / intercultural / multicultural relationships - long-distance relationships - communication across languages - culture clash and misunderstandings - moving abroad for love - family expectations - identity and belonging - finding community abroad - women-centered support - real stories from intercultural couples - practical relationship and communication guidance The site should feel like a blend of: - podcast archive - editorial storytelling platform - women’s support community - workshop / coaching funnel - lead magnet funnel ================================ HOMEPAGE INFORMATION ARCHITECTURE ================================ Build the homepage with this flow: 1. HERO SECTION Purpose: - instantly communicate who this is for - establish emotional resonance - drive the primary CTA Requirements: - strong emotional headline for women navigating intercultural love - supportive subheadline explaining what International Love Story is - primary CTA: join the community - secondary CTA: get the free communication guide (or actual lead magnet title if found) - tertiary CTA: listen to the podcast - visually feature Christina/Tina if image assets are available - premium, warm, editorial look - must feel highly intentional on mobile 2. TRUST / SOCIAL PROOF STRIP Purpose: - establish legitimacy quickly Include: - language like: - real stories - intercultural relationship support - practical communication tools - community for women - if supported by harvested data, mention: - 100+ podcast episodes or softer wording like “a growing library of conversations” - keep this concise and scannable 3. SIGNATURE MAP / WORLD DISCOVERY SECTION Purpose: - create the memorable “wow” experience - visually reinforce the global relationship concept Concept: - each episode is represented by two connected points - the connection should evoke a “red thread” / “red string of connection” - the two points can represent: - host / Christina location context - guest / partner / featured story location - for MVP, a polished 2D world map or stylized faux-globe is acceptable if a full globe is overkill - prioritize clarity, beauty, and touch usability over visual gimmicks Requirements: - visible connection lines between two places per story - highlighted pins on tap / click - clear selected state - smooth, lightweight interaction - mobile-friendly layout 4. SEARCH / FILTER DISCOVERY Purpose: - help visitors find relevant stories by emotional relevance first Search and filter priority: 1. themes 2. country names 3. episode titles 4. guest names Requirements: - search input - theme chips / filter pills - country-based discovery - results list tied to map selection - discovery should feel inviting, not like an admin dashboard Theme chips should include: - communication - language barriers - long-distance - family - moving abroad - identity - friendship - paperwork / visas - multilingual children - cultural adjustment 5. EPISODE DETAIL MODAL Purpose: - turn discovery into deeper engagement Trigger: - clicking a map connection - clicking a search result - clicking a featured episode card Modal should include: - episode title - guest name(s) - countries involved - short summary - theme tags - outbound buttons (listen / watch / learn more) - optional secondary CTA into community or lead magnet Rules: - mobile-first modal layout - large tap targets - no embedded players in MVP - outbound links only 6. FEATURED OFFERS / FUNNEL SECTION Purpose: - convert visitors into the core business outcomes Build distinct cards/blocks for: - community - free communication guide / lead magnet - workshops - coaching - “tell your story” / story application Each item should include: - title - short benefit-oriented description - direct CTA button - supporting microcopy Hierarchy: - community first - lead magnet second - workshops/coaching next - story submission as a narrative/community expansion CTA 7. ABOUT CHRISTINA / TINA SECTION Purpose: - humanize the brand and create personal trust Include: - short personal narrative - bridge from lived experience to practical support - position her as relatable, credible, and emotionally grounded - if harvested content gives exact phrasing, use that - otherwise write tasteful copy consistent with the brand 8. PODCAST SECTION Purpose: - highlight the podcast as a major trust and discovery asset Include: - description of what listeners get - platform buttons linking out to real platform destinations - featured or recent episodes - support the brand story without overpowering the main conversion funnel 9. FINAL CTA SECTION Purpose: - end with a clear emotional conversion moment Requirements: - strong closing statement - primary CTA: join the community - secondary CTA: free guide - optional CTA: tell your story ================================ SITE CONTENT REQUIREMENTS ================================ The MVP should include both media and offers: - podcast archive - free communication guide / lead magnet - community for women - workshops / coaching - “tell your story” application All guest names and locations are intended to be public on the map. Outbound links are acceptable and preferred over heavy embeds. ================================ DATA MODEL REQUIREMENTS ================================ Create a structured content layer that powers the UI. At minimum define: - episodes[] - featuredThemes[] - countries[] - offers[] - testimonials[] (real if available, tasteful placeholder if not) - ctas[] - brand metadata Each episode entry should support: - id - title - slug - guestName - guestCountry - hostCountry - connectedCountries[] - themes[] - summary - platformLinks - featuredImage - publishedAt - isFeatured - source - placeholder (boolean if needed) Seed content requirement: - create at least 8 to 12 compelling episode entries - use real episode data if accessible - otherwise create curated structured seed entries aligned with harvested themes and mark uncertain fields clearly - the map must not be empty ================================ DESIGN DIRECTION ================================ The design should feel: - warm - intimate - feminine - editorial - story-driven - globally connected - polished and emotionally resonant Avoid: - default bland startup layouts - overly dark moody luxury aesthetics - generic pastel wellness sameness - flat white pages with random purple gradients Preferred palette direction: - soft cream / ivory backgrounds - terracotta / clay / muted rose accents - deep olive / warm espresso / ink contrast tones Typography: - choose expressive, intentional type - avoid boring default system-only feel - the typography should feel human and premium Background and atmosphere: - use subtle texture, layered gradients, soft glows, shapes, map overlays, or paper-like warmth - create section contrast so the page feels composed, not monotonous Motion: - hero reveal - selected map connection emphasis - modal transitions - staggered content reveals if useful - keep motion tasteful and not distracting ================================ UX RULES ================================ Mobile-first is a hard requirement. The site must work well on small screens: - readable hierarchy - comfortable spacing - clear thumb-friendly buttons - usable filters - modal interactions that don’t feel cramped - no tiny map hit targets A first-time visitor should immediately understand: - who this is for - what International Love Story is - what to click next ================================ COPY DIRECTION ================================ Write copy for women navigating intercultural relationships. Center the emotional realities: - feeling misunderstood across languages and cultures - rebuilding life in a new country - loneliness and missing community - relationship strain caused by distance, migration, or differing norms - wanting practical communication tools - wanting to feel less alone The copy should make visitors feel: - seen - soothed - guided - invited into a real community Do not write: - hollow motivational fluff - vague “empowerment” text - generic coaching copy detached from the intercultural-love niche ================================ TECHNICAL EXECUTION RULES ================================ - Use the existing project/app in the workspace if there is one. - Prefer modifying the existing frontend app instead of creating unnecessary duplicates. - Build the site so it can be previewed immediately. - Use the harvested content as the primary source of truth. - Where data is missing, fill gaps with tasteful placeholders and clearly structured code. - Keep architecture simple and fast to iterate. - If useful, separate data from presentation cleanly so later content updates are easy. ================================ DELEGATION WORKFLOW (RECOMMENDED) ================================ Use this execution pattern unless the codebase proves it needs a different one: Step 1: - Send `gemini` a harvesting task for the provided links. - Ask it to return: - CTA inventory - offer inventory - available brand language - platform links - visual/style signals - uncertainties / blocked pages Step 2: - In parallel, send `codex` a codebase inspection task. - Ask it to identify: - the correct app to modify - the frontend stack - where to place structured data files - the cleanest path to implement the homepage and interactions Step 3: - After harvest results come back, have `codex` implement: - data layer - homepage structure - map/discovery UI - modal interaction - CTA wiring - mobile-first layout Step 4: - Send `gemini` a content synthesis task using harvested material. - Ask it to draft/refine: - hero copy - trust strip copy - offer section copy - about section copy - final CTA copy - Then integrate the best version into the app Step 5: - Send `deepseek-code` a focused second-opinion task. - Ask it to review: - map/search/filter interaction logic - data schema robustness - mobile UX risks - any obvious implementation improvements Step 6: - Integrate only the useful improvements. - Do not churn endlessly. - Produce a coherent final build. ================================ DELIVERABLES ================================ By the end of this task, you should have: 1. A harvested source-data layer - brand, CTAs, offers, podcast metadata, assets, notes 2. A functioning MVP site implementation - homepage and supporting sections - interactive map/discovery concept - modal-based story detail interaction - real CTA destinations wired in 3. Clean structured content - enough seeded/real data to make the experience feel complete 4. A previewable result - not just files, but something that can be run / viewed in the local app stack DECISION RULES ================================ - If a source page blocks access, use the best accessible public metadata or previews you can get. - Prefer shipping a coherent, beautiful, functional prototype over waiting for perfect data. - Make strong product decisions without unnecessary questions. - If exact information is unavailable, use conservative placeholders and clearly structure them for future replacement. - Do not stop after research. Research is only phase 1. Build in phase 2. - Delegate substantial tasks, but keep final control and integrate the outcome yourself. ================================ SUCCESS CRITERIA ================================ The finished result should feel like a real launchable prototype for International Love Story: - emotionally compelling - clearly targeted to women in intercultural relationships - conversion-first - community-forward - story-driven - globally themed - visually distinctive - mobile-first - immediately useful Do the work now. One operational note: if deepseek-code on this machine is not fully functional as a true harness-backed worker, Pipo should still use codex and gemini as the main workers and treat deepseek-code as optional rather than blocking progress. MAKE SURE YOU USE THE TAILSCALE EXIT NODE, PIXEL 6A, IF YOU ENCOUNTER ANY PROBLEMS WITH ACCESSING ANY OF THE WEBSITES OR LINKS AFOREMENTIONED. HERE'S A TRANSCRIPT OF THE ORIGINAL BRIEF, FYI: 1. Is this a brand-new site, or a redesign/replacement of an existing official site? Tina (chrisTina) already has a website with some information, but not so much. Unfortunately this website is not available/unpublished so assume this is a brand new site.. 2. What is the primary goal of the site? Pick the top priority: #1 drive community signups #2 convert into paid coaching/workshops #3 collect emails for the lead magnet #4 grow podcast listens/views 3. For the globe pins, what exactly is one pin? Options: - two connected pins per episode (country A + country B) (like a silver lining/red line? what is the name of that saying like we are all connected etc.. with a red string) 4. Do you already have a structured list of episodes and guests? For the map/search to work well, we need per episode: you should be able to get this from spotify, as it is quite clear and you can go through it. 5. Should search work over: Let's work on prioritization: #1 themes (visa, language barriers, long distance, family, moving abroad, identity, etc.) #2 country names #3 episode titles #4 guest names 6. When a user clicks a result, what should happen? Choose the preferred behavior: - open a modal with the episode details + buttons. It should work on mobile though! 7. Do you want embedded players, or just outbound links? Outbound links is OK, the idea after all is for listeners or viewers to subscribe. 8. Should the map be the homepage hero, or below a strong landing section? A better conversion-oriented structure is usually: - Hero: emotional positioning + CTA - Then interactive map - Then featured episodes / lead magnet / community If you want the map to be the “wow” moment, we can invert that. response: this is fine as suggested 9. What tone should the design have? Which is closest: - warm / intimate / feminine This will heavily influence typography, colors, and imagery. 10. Do you have brand assets ready? Needed if available: - logo - fonts - brand colors - Christina headshots - podcast cover art - episode thumbnails Without these, the first version will be a strong concept but still a placeholder brand-wise. We have all these but you can either extract them from the links provided or you can put placeholders. 11. Do you want an admin-editable CMS in phase 1, or a curated static/data-file site first? Choices: - MVP first: static site + JSON dataset, fast and simple - CMS-backed: easier long-term content management, slower to build For a prototype, I’d start with static + structured JSON. response: lets' start with the prototype, MVP first. 12. Are all guest names and locations meant to be public on the map? Yes. 13. Do you want the site to include only podcast content, or also Christina’s offers? Possible sections: - Podcast archive - Free communication guide - Community for women - Workshops / coaching - “Tell your story” application This affects whether the site is primarily media, lead-gen, or both. YES TO ALL THANK YOU LOVE YOU <3 14. Is mobile-first a hard requirement? YES