# Features

Various features are available to enable you to quickly design, preview and publish data-driven applications

***

[**Application**](/features/application.md)

<div align="left"><figure><img src="/files/xBByGLg2oObRQuSW7GtO" alt=""><figcaption></figcaption></figure></div>

The Application contains [*Pages*](/features/pages.md), [*Scripts*](/features/scripts-and-event-handlers.md), settings and [*Connectors*](/connectors.md).

***

[**Create Form**](/features/create-a-form.md)

<div align="left"><img src="/files/Am1cnX94jjmLG968aRwE" alt=""></div>

The Create Form wizard is used to quickly create forms for adding or editing data.

***

[**Embedded Files**](/features/embedded-files.md)

<div align="left"><img src="/files/N1gHr6ynLLMsbepzuQtL" alt=""></div>

Files can be embedded in an application to be used in different ways.

***

[**Events**](/features/events.md)

<div align="left"><img src="/files/uv2tSfL3L00pS9rhXFdm" alt=""></div>

Events can be added to [*Pages*](/features/pages.md) and controls to provide specific functionality and behaviours.

***

[**Expression Editor**](/features/expression-editor.md)

<div align="left"><img src="/files/m1IFuMl9BGG8uHlbBtWl" alt=""></div>

Use the Expression Editor to assist you when complex expressions are required to create the property values of controls and actions.

***

[**Mappings**](/features/mappings.md)

<div align="left"><img src="/files/pD3lWnCIhaEazW2XLcWx" alt="" height="64" width="64"></div>

Use the Mappings Editor to assist when mapping List properties.

***

[***Pages***](/features/pages.md)

<div align="left"><img src="/files/7gJqH8dlWQ0AmEg8BDDD" alt="" height="64" width="64"></div>

Pages are what makes up Stadium applications. Create [*Pages*](/features/pages.md) and provide navigation to allow users to browse the site.

***

[**Preview**](/features/preview.md)

<div align="left"><img src="/files/E2WClMxDkpujrEkwfiZg" alt=""></div>

Preview your application to verify correct display and behaviour before you publish it.

***

[**Publish**](/features/publish.md)

<div align="left"><img src="/files/uiUgWQAUnbHfiqYwv3Sr" alt=""></div>

Applications can be published to your Stadium Application Manager from within Stadium Designer.

***

[***Scripts*****/ Event Handlers**](/features/scripts-and-event-handlers.md)

<div align="left"><img src="/files/53iTnBKjhtUlYnwfJeBR" alt=""></div>

*Scripts* and event Handlers can be added to a load, click or change Event to provide specific behaviours.

***

[**Settings**](/features/settings.md)

<div align="left"><img src="/files/lQJVVt37IDYX2wMKgB60" alt=""></div>

Settings are static values that cannot be changed. If you use settings for environment-specific values, such as file paths, it becomes easier to migrate applications between environments.

***

[**Styles**](/features/styles.md)

<div align="left"><img src="/files/FhbEc4GUkEC7HEerg9Wk" alt=""></div>

Use the [Styles](/features/styles.md) Editor to create the styles that determine how your [*Pages*](/features/pages.md) and controls will be displayed.

***

[**Style Sheet**](/features/stylesheet.md)

<div align="left"><img src="/files/RgWjSDy5G4FAaVWVmDdA" alt=""></div>

You can paste the contents of a CSS stylesheet into the StyleSheet editor to style the way your [*Pages*](/features/pages.md) and controls will be displayed.

***

[**Templates**](/features/templates.md)

<div align="left"><img src="/files/uW1m3wReCTDiGzVKCOQH" alt=""></div>

Templates are used to display specific controls on multiple screens in your application without having to add those controls to each page.

***

[**Types**](/features/types.md)

<div align="left"><img src="/files/i5XOlTcuizTOf8DjL11p" alt=""></div>

Types can be used to create variables of different types that can be used in your application's processing of data.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stadium.software/features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.