We need to translate the article content into Spanish, keeping all formatting, markdown, code, URLs, product names unchanged. 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 unchanged. Keep tone and structure same.

We must translate all text inside tags, but not code or URLs. Also keep placeholders like Screenshot placeholder: ... unchanged. The alt text should be translated? The alt text is part of the content. The instruction says translate only prose, descriptions, explanatory text. The alt attribute is descriptive text, so we should translate it. But the alt text is inside the HTML tag; we can translate it. The placeholder alt text is "Screenshot placeholder: Song Requests dashboard with incoming requests". That is descriptive, so translate. Similarly for other alt texts.

Also the

etc. Titles should be translated. The article has

tags. We need to translate the headings. The

headings too. The
etc. The
    items. The
      items. The headings and rows. The 
       blocks contain code or text that may need translation? The code block includes "Welcome to Sarah & Mike's Wedding! Request your favorite songs and we'll try to play them tonight." That is a string that should be translated. The guidelines block also contains bullet list of guidelines; that is text that should be translated.
      

      Also the "Next Steps" section has 
       headings and paragraphs with links. The links themselves should remain unchanged. The anchor text should be translated.
      

      Also the final paragraph.
      

      We must keep the 
       as is.
      

      We need to keep the  tags inside text. For example, What you'll achieve: etc. We need to translate the content inside  tags.
      

      Also the 
       tags contain Note: etc. Translate.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Privacy Note: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Privacy Note: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Privacy Note: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Also the 
       with Pro Tip: etc.
      

      Ok.
      

      Stop.
      

      We need to translate all text.
      

      Let's go through article.
      

      Title: Set Up Song Requests for Weddings, Events, and DJ Gigs
      

      We need to translate title. But the title is not inside tags? The article content starts with 
      Introduction
      . The title might be outside. We should translate the title line: "Set Up Song Requests for Weddings, Events, and DJ Gigs". That should be translated to Spanish: "Configura Solicitudes de Canciones para Bodas, Eventos y Gigs de DJ". Keep same structure? The title is not in tags. We can output it as plain text. But the instruction says provide ONLY the translated article content, keeping all formatting and structure identical. The title was part of the article content. So we need to translate it. So we output the title line, then the rest.
      

      Let's translate.
      

      "Set Up Song Requests for Weddings, Events, and DJ Gigs" -> "Configura Solicitudes de Canciones para Bodas, Eventos y Gigs de DJ"
      

      Now the article content.
      

      Introduction
      


      Song Requests is a game-changing feature for DJs and event hosts. Instead of guests walking up to you mid-set or shouting requests over the music, they simply scan a QR code and submit requests from their phones.
      


      Translate: "Song Requests es una característica revolucionaria para DJs y anfitriones de eventos. En lugar de que los invitados se acerquen a ti a mitad de la actuación o griten solicitudes sobre la música, simplemente escanean un código QR y envían solicitudes desde sus teléfonos."
      

      What you’ll achieve:
      


      Translate: "
      Lo que lograrás:
      "
      

         list items:


      • Guests request songs from their phones via QR code
        •  -> "Los invitados solicitan canciones desde sus teléfonos mediante código QR"


      • Manage requests with approve, reject, and queue options
        •  -> "Gestiona las solicitudes con opciones de aprobar, rechazar y poner en cola"


      • Auto-detect when requested songs are played
        •  -> "Detección automática cuando se reproducen las canciones solicitadas"


      • Collect contact info for future event marketing
        •  -> "Recopila información de contacto para marketing de eventos futuros"


      • Professional request management without interruptions
        •  -> "Gestión profesional de solicitudes sin interrupciones"


      


      Screenshot placeholder: Song Requests dashboard with incoming requests
      


      Translate alt: "Captura de pantalla placeholder: Panel de Solicitudes de Canciones con solicitudes entrantes"
      

      Prerequisites
      


      Before starting, make sure you have:
      


        


      • macOS 13.0 (Ventura) or later
        •  -> keep same.


      • Song Overlays Pro installed from the Mac App Store
        •  -> keep product name unchanged.


      • Active Song Requests subscription ($5.99/month via Mac App Store)
        • 


      • A way to display the QR code (screen, projector, or printed)
        • 


      


      


      Note: The core app ($9.99 one-time) handles song detection. Song Requests is an optional subscription add-on.
      


      Translate: "
       
      Nota: La aplicación principal ($9.99 una sola vez) gestiona la detección de canciones. Song Requests es un complemento de suscripción opcional.
      "
      

      


      How Song Requests Works
      


      Here’s the flow from your guest’s perspective:
      


      Translate: "
      Este es el flujo desde la perspectiva de tu invitado:
      "
      

        


      1. Guest sees your QR code (on screen, table tent, or projector)
        2.  -> "El invitado ve tu código QR (en pantalla, mesa de invitado o proyector)"


      2. They scan it with their phone camera
        3.  -> "Lo escanean con la cámara de su teléfono"


      3. A web page opens where they can search for songs
        4.  -> "Se abre una página web donde pueden buscar canciones"


      4. They submit their request (optionally with their name/contact)
        5.  -> "Envian su solicitud (opcionalmente con su nombre/contacto)"


      5. You see the request instantly on your Mac
        6.  -> "Ves la solicitud instantáneamente en tu Mac"


      6. You approve, queue, or play the song
        7.  -> "Aprobás, pones en cola o reproduces la canción"


      7. When you play it, the system auto-detects and marks it complete
        8.  -> "Cuando la reproduces, el sistema la detecta automáticamente y la marca como completada"


      


      No app download required for guests — it’s all web-based.
       -> "No se requiere descarga de aplicación para los invitados: todo es web."


      Step 1: Enable Song Requests
      


      First, activate the Song Requests feature in Song Overlays Pro.
      


      Screenshot placeholder: Song Requests enable toggle
      


      Translate alt: "Captura de pantalla placeholder: Alternar habilitación de Solicitudes de Canciones"
      

        


      1. Open Song Overlays Pro
        2. 


      2. Click Song Requests in the sidebar
        3. 


      3. Click Subscribe or Start Free Trial if you haven’t already
        4. 


      4. Once subscribed, toggle Enable Song Requests to on
        5. 


      5. The server will start and generate your unique QR code
        6. 


      


      Step 2: Configure Your Request Settings
      


      Customize how requests work for your event.
      


      Screenshot placeholder: Song Requests settings panel
      


      Translate alt: "Captura de pantalla placeholder: Panel de configuración de Solicitudes de Canciones"
      

      Basic Settings
      


        


      1. Event Name — Displayed on the request page (e.g., “Sarah & Mike’s Wedding”) 
        2.  -> "Nombre del Evento — Se muestra en la página de solicitud (p. ej., “Boda de Sarah & Mike”)"


      2. Request Limit — Maximum requests per guest (prevents spam)
        3.  -> "Límite de Solicitud — Máximo de solicitudes por invitado (previene spam)"


      3. Allow Duplicates — Whether the same song can be requested twice
        4.  -> "Permitir Duplicados — Si la misma canción puede ser solicitada dos veces"


      4. Require Contact Info — Collect guest emails/names (great for marketing)
        5.  -> "Requerir Información de Contacto — Recopila correos/e nombres de invitados (excelente para marketing)"


      


      Request Statuses
      


      Song Overlays Pro uses 8 status options to manage requests:
      Status Description
      New Just received, awaiting review
      Queued Approved and in your queue
      Playing Currently being played
      Played Completed (auto-detected)
      Rejected Not appropriate for this event
      Maybe Later Good request, saving for later
      Already Played Song was already played earlier
      Not Available Don’t have this track

      We need to translate the table content: Status and Description headings, and each row's description.

      Status column: keep status names? They are in Spanish? The status names are in English: New, Queued, Playing, Played, Rejected, Maybe Later, Already Played, Not Available. Should we translate