> 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/comandos-de-powershell/new-udeditor.md).

# New-UDEditor

New-UDEditor incrusta un editor de contenido enriquecido Editor.js en PowerShell Universal para crear contenido de página estructurado y basado en bloques.

### Sinopsis

Crea un editor Editor.JS.

### Sintaxis

```powershell
New-UDEditor [[-Id] <String>] [[-Data] <Hashtable>] [[-OnChange] <Endpoint>] [[-Format] <String>] [[-PublishedFolder] <String>] [<CommonParameters>]
```

### Descripción

Crea un editor Editor.JS.

### Parámetros

#### -Id

El id del editor. Su valor predeterminado es un nuevo GUID.

```
Required?                    false
Position?                    1
Default value                ([Guid]::NewGuid())
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Data

Los datos que se van a usar en el editor.

```
Required?                    false
Position?                    2
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -OnChange

El endpoint al que se llama cuando el editor cambia.

```
Required?                    false
Position?                    3
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Format

El formato de los datos. Puede ser json o html.

```
Required?                    false
Position?                    4
Default value                json
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -PublishedFolder

Una carpeta publicada a la que subir ficheros. Es obligatoria para el plugin de subida de imágenes.

```
Required?                    false
Position?                    5
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Parámetros comunes

Este cmdlet admite los parámetros comunes: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable y OutVariable. Para más información, consulte [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Salidas

### Ejemplos

#### Ejemplo 1: editor básico

```powershell
New-UDEditor -Id 'editor1'
```

Un editor básico.

#### Ejemplo 2: editor HTML

```powershell
New-UDEditor -Id 'editor2' -Format 'html'
```

Un editor que usa HTML.

#### Ejemplo 3: OnChange

```powershell
New-UDEditor -Id 'editor3' -OnChange {
    Show-UDToast $Body
}
```

Un editor con un bloque de script OnChange.

#### Ejemplo 4: HTML

```powershell
New-UDEditor -Format html -OnChange {
    Set-UDElement -Id 'test' -Content {
        $body
    }
}
New-UDElement -Tag pre -Id 'test'
```

Un editor que actualiza una etiqueta pre con el contenido HTML.


---

# 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/comandos-de-powershell/new-udeditor.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.