> 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/powershell-commands/publish-psustaticapp.md).

# Publish-PSUStaticApp

Publish-PSUStaticApp exports a PowerShell Universal app definition as a static site that can be hosted outside of PowerShell Universal.

## SYNOPSIS

Publishes a static app based on the PowerShell Universal app framework.

## SYNTAX

```
Publish-PSUStaticApp -Definition <ScriptBlock> -DestinationPath <String> [-Force]
 [<CommonParameters>]
```

## DESCRIPTION

Publishes a static app based on the PowerShell Universal app framework. Static apps can be hosted outside of PowerShell Universal.

## EXAMPLES

### Example 1

```powershell
PS C:\> Publish-PSUStaticApp -Definition { New-UDApp -Content { New-UDTypography "Hello!" } } -DestinationPath 'C:\MyStaticApp'
```

Creates a static app in the path `C:\MyStaticApp` based on the definition provided.

## PARAMETERS

### -Definition

The definition of the static app. This is a script block that contains the definition of the app. The script block should contain a call to `New-UDApp` with the content of the app.

```yaml
Type: ScriptBlock
Parameter Sets: (All)
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -DestinationPath

The path to the directory where the static app will be published. This path must be a valid file system path.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Force

If specified, the cmdlet will overwrite any existing files in the destination path without prompting for confirmation.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable, and -ProgressAction. For more information, see [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### None

## OUTPUTS

### System.Object

## NOTES

## RELATED LINKS


---

# 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/powershell-commands/publish-psustaticapp.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.