> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-developers/componentes-web/webrtc/slots.md).

# Slots

Los slots son espacios que contienen elementos por defecto, pero que podrás reemplazar con tus propios elementos. Por ejemplo, para reemplazar los botones de nuestro `WebRTC` deberás añadir:

{% code lineNumbers="true" %}

```html
<videsk-webrtc>
    <div slot="slot-name">cuxtom content</div>
</videsk-webrtc>
```

{% endcode %}

Los `slots` disponibles son:

## Botones

El listado de botones accionables como compartir pantalla, micrófono, cámara, colgar, pantalla completa, rotar cámara y chat se puede personalizar o incluso eliminar.

* `button-screen`: botón de compartir pantalla
* `button-mic`: botón de micrófono
* `button-cam`: botón de cámara
* `button-hangup`: botón de colgar
* `button-toggle-camera`: botón de rotar cámara
* `button-chat`: botón de chat
* `button-fullscreen`: botón de pantalla completa

<figure><img src="https://294851947-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ma4POQR_-BPjQwRwhXE-1769347644%2Fuploads%2F6kaZvmQgQAqAPkHi4Oox%2Fimage.png?alt=media&amp;token=40df9637-9ce7-4377-8719-48b6fbc752e6" alt=""><figcaption><p>Botones disponibles por defecto</p></figcaption></figure>

{% hint style="info" %}
Los botones de cambio de cámara y compartir pantalla automáticamente se mostrarán si la función está disponible en el navegador, de lo contrario no se mostrará.
{% endhint %}

{% code lineNumbers="true" %}

```html
<videsk-webrtc>
    <button slot="button-screen">Compartir pantalla</button>
    <button slot="button-mic">Micrófono</button>
    <button slot="button-cam">Cámara</button>
    <button slot="button-hangup">Colgar</button>
    <button slot="button-toggle-camera">Rotar cámara</button>
    <button slot="button-chat">Chat</button>
    <button slot="button-fullscreen">Pantalla completa</button>
</videsk-webrtc>
```

{% endcode %}

Puedes utilizar cualquier elemento HTML dentro de la etiqueta `videsk-webrtc` incluso elementos complejos como:

{% code lineNumbers="true" %}

```html
<videsk-webrtc>
    <div slot="button-hangup">
        <i class="phone" />
        <span class="tooltip">Colgar</span>
    </div>
</videsk-webrtc>
```

{% endcode %}

## Iconos

Puedes personalizar los íconos:

* `participants-toggle-icons`

```html
<videsk-webrtc>
  <div slot="participants-toggle-icons">
     <!-- Custom icons -->
  </div>
</videsk-webrtc>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.videsk.io/es-developers/componentes-web/webrtc/slots.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
