> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/es/aplicaciones/components/utilities/head-element.md).

# Elemento head

Utilice el cmdlet New-UDHelmet en PowerShell Universal para inyectar etiquetas de head como elementos script, link y style para cargar JavaScript y CSS externos.

Puede utilizar el cmdlet `New-UDHelmet` para añadir etiquetas de elementos `<head>` como `<script>` y `<style>` a sus páginas. Esto resulta útil para incluir JavaScript o CSS alojados externamente.

## JavaScript

Puede cargar JavaScript utilizando la etiqueta script con el atributo `src`. Tenga en cuenta que pueden estar vigentes limitaciones sobre los recursos entre sitios y que quizá tenga que ajustar la configuración del servidor web para admitirlo.

```powershell
New-UDApp -Content {
    New-UDHelmet -Tag 'script' -Attributes @{ src = "https://www.mycdn.com/site.js" } 
}
```

## CSS

Puede cargar CSS utilizando la etiqueta `link`.

```powershell
New-UDHelmet -Tag 'link' -Attributes @{ 
    rel = 'stylesheet' 
    href = "mystylesheet.css"
} 
```

## Estilos

Puede utilizar una etiqueta `style` para proporcionar estilos directamente.

```powershell
New-UDHelmet -Tag 'style' -Attributes @{ 
    type = 'text/css' 
} -Content "body { background-color: 'red' }"
```

## Aplicación

También puede cargar hojas de estilo y scripts directamente desde la aplicación.

```powershell
New-UDApp -Content {

} -Stylesheets "mysheet.js" -Scripts "mysite.js"
```


---

# 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.devolutions.net/powershell-universal/es/aplicaciones/components/utilities/head-element.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.
