> 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/fr/commandes-powershell/new-udstyle.md).

# New-UDStyle

New-UDStyle applique des règles CSS personnalisées à un composant ou à une page entière dans PowerShell Universal pour un contrôle précis du style visuel.

### Résumé

Appliquer un style CSS à un composant.

### Syntaxe

```powershell
New-UDStyle [-Id <String>] -Style <String> [-Tag <String>] [-Content <ScriptBlock>] [<CommonParameters>]

New-UDStyle [-Id <String>] -Sx <Hashtable> [-Component <String>] [-Tag <String>] [-Content <ScriptBlock>] [<CommonParameters>]
```

### Description

Appliquer un style CSS à un composant.

### Paramètres

#### -Id

L'ID de ce composant.

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

#### -Style

Le style CSS à appliquer

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

#### -Sx

Une table de hachage de propriétés CSS adaptées au thème.

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

#### -Component

Le composant racine auquel appliquer le composant Sx.

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

#### -Tag

La balise HTML externe à utiliser.

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

#### -Content

Le contenu de ce style.

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

#### Paramètres communs

Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, consultez [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Sorties

### Exemples

#### Exemple 1 : Style

```powershell
New-UDStyle -Style 'color: red; background-color: black' -Content {
   New-UDTypography -Text "This is red"
}
```

Appliquer un style CSS à un composant.

\[Component("Style", "Css3", "Creates a new card.")]


---

# 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/fr/commandes-powershell/new-udstyle.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.
