We need to translate the article content into French, keeping all formatting, markdown, code, URLs, product names unchanged. We must keep product names like Song Overlays Pro, OBS, Discord, Shazam, TouchOSC, QLab, Resolume unchanged. Also keep code examples, command lines, URLs, technical terms exactly as they are. Keep markdown formatting and structure intact. Translate only prose, descriptions, explanatory text. Use consistent terminology. Keep HTML/markdown syntax exactly. Keep links and references unchanged. Maintain same tone and structure.

We need to translate the article content. The article content includes headings, paragraphs, lists, tables, code blocks, etc. We must translate all text except product names, code, URLs, etc.

We need to keep the placeholders like ... unchanged. Also keep the

tags. Also keep the 
 blocks unchanged except the content inside must be translated? The code block includes text like "Welcome to Sarah & Mike's Wedding! Request your favorite songs and we'll try to play them tonight." This is not code but a text block. The instruction says keep code examples, command lines, URLs, and technical terms exactly as they are. The 
 block is not code but a message. Should we translate it? The instruction says translate only prose, descriptions, and explanatory text. The 
 block is a custom message. It's not code, but it's content. Should we translate it? It's part of the article. It's a custom welcome message. It is not code per se. But the instruction says keep code examples exactly. This is not code. It's a message. So we should translate it. But we need to keep the formatting. So we will translate the content inside the 
 block.


Also the 
 block for guidelines. We should translate that too.


Also the table of statuses: we need to translate the Status and Description columns. Keep the status names? The status names are in English: New, Queued, Playing, Played, Rejected, Maybe Later, Already Played, Not Available. Should we translate them? They are status options used by the app. The instruction says keep product names unchanged, but these are not product names. They are status options. Should we translate them? The instruction says use consistent terminology. The status options are part of the app. The article uses them. Probably we should translate them to French? But the instruction says keep product names unchanged. It doesn't mention status names. But we want to translate the article. The status names are part of the app's UI. They might be displayed in the app. The article might mention them. The article is in English. We can translate them to French. But the instruction says "Use consistent terminology throughout - maintain a translation glossary." We don't have a glossary. But we can decide to translate them. However, the article might be read by French users. They might see the status names in the app. The article might mention them. But if we translate them, it might mismatch the actual status names in the app. But the article is a guide. It might be okay to translate them. But the instruction didn't explicitly say to keep status names unchanged. So we can translate them. But we need to be consistent. So we will translate the status names to French. But we need to decide the translations:


    

  • New -> Nouveau
    • 

  • Queued -> En file d'attente
    • 

  • Playing -> En cours de lecture
    • 

  • Played -> Joué
    • 

  • Rejected -> Rejeté
    • 

  • Maybe Later -> Peut-être plus tard
    • 

  • Already Played -> Déjà joué
    • 

  • Not Available -> Indisponible
    • 



But we need to keep the table structure. We'll translate the content accordingly.


Also the bullet points: "Guests request songs from their phones via QR code" etc. We'll translate.


Also the headings: 
Introduction
 stays same but we translate the content inside.


Also the 
 note: "Note: The core app ($9.99 one-time) handles song detection. Song Requests is an optional subscription add-on." We'll translate.


Also the "Step 1: Enable Song Requests" etc. We'll translate.


Also the  alt text: "Screenshot placeholder: Song Requests dashboard with incoming requests" - we can translate alt text? The alt text is part of the article. We can translate it. But the instruction says keep all code examples, command lines, URLs, and technical terms exactly as they are. The alt text is not code. It's descriptive. We can translate it. But we need to keep the alt text in French. So we will translate alt text accordingly.


Also the 
 note: "Pro Tip: Test your QR code before the event! Scan it yourself to ensure it works from various distances." We'll translate.


Also the 
 note: "Privacy Note: Only collect contact info if you have a legitimate use for it. Be transparent with guests about how their info will be used." We'll translate.


Also the "Event-Specific Tips" section: we translate bullet points.


Also the "Troubleshooting" section: we translate each subheading and bullet points.


Also the "Advanced: Request Page Customization" section: we translate.


Also the "Next Steps" section: we translate.


Also the final paragraph: "You're all set! Song Requests transforms how you handle audience interaction. No more shouted requests, no more forgetting what guests asked for — just smooth, professional request management that makes every event better." We'll translate.


Also the links: Learn about OBS overlays - we need to translate the link text but keep the href unchanged. So "Learn about OBS overlays" becomes "En savoir plus sur les superpositions OBS" or "Découvrez les superpositions OBS". We'll translate.


Also Set up Discord integration -> "Configurez l'intégration Discord".


Also Join Discord -> "Rejoignez Discord".


Also the 
 stays same.


Also the final 
You’re all set! ...
 -> translate.


Also the 
Step 1: Enable Song Requests
 etc. We'll translate.


Also the 
     steps: we translate each step.
    

    Also the 
       steps for Step 2: Configure Your Request Settings: we translate.
      

      Also the 
      Basic Settings
       etc.
      

      Also the 
      Request Statuses
       etc.
      

      Also the table: we translate.
      

      Also the 
      Step 3: Generate and Display Your QR Code
       etc.
      

      Also the 
      Display Options
       etc.
      

      Also the 
       Pro Tip: ... -> "Astuce Pro: ..."
      

      Also the 
      Step 4: Manage Incoming Requests
       etc.
      

      Also the 
      The Request Queue
       etc.
      

      Also the 
      Quick Actions
       etc.
      

      Also the 
      Keyboard Shortcuts
       etc.
      

      Also the 
      Step 5: Set Up Auto-Detection
       etc.
      

      Also the 
      Step 6: Display Request Status (Optional)
       etc.
      

      Also the 
      Step 7: Export Guest Contacts
       etc.
      

      Also the 
       Privacy Note: ... -> "Note de confidentialité: ..."
      

      Also the 
      Event-Specific Tips
       etc.
      

      Also the 
      Weddings
       etc.
      

      Also the 
      Corporate Events
       etc.
      

      Also the 
      Club/Bar Gigs
       etc.
      

      Also the 
      Troubleshooting
       etc.
      

      Also the 
      Guests Can't Scan the QR Code
       etc.
      

      Also the 
      Requests Not Appearing
       etc.
      

      Also the 
      Auto-Detection Not Working
       etc.
      

      Also the 
      Too Many Requests
       etc.
      

      Also the 
      Advanced: Request Page Customization
       etc.
      

      Also the 
      Custom Welcome Message
       etc.
      

      Also the 
      Request Guidelines
       etc.
      

      Also the 
      Theming
       etc.
      

      Also the 
      Next Steps
       etc.
      

      Also the 
      Display What's Playing
       etc.
      

      Also the 
      Send to Discord
       etc.
      

      Also the 
      Join the Community
       etc.
      

      Also the final 
       and final paragraph.
      

      We must keep all formatting identical. So we need to preserve the 
      , 
      ,