> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peektag.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Inputs

> Understand the most common input types used in manual refinement, including editor, toggles, selects, uploads, and dates.

# Common Inputs

This page brings together the most common input types designers use during manual refinement.

These inputs are usually simple, fast to fill out, and useful when you do not need a large structured form. They help the designer update one part of the experience quickly without opening a more complex setup.

## Text

Use **Text** when the designer only needs to enter one short and simple value.

This is the best choice for small inputs such as:

* a title
* a short label
* a name
* a tagline
* a quick value that does not need formatting

If the content is short and straightforward, **Text** is usually the fastest and cleanest option.

![Text Placeholder](C:/Users/amirt/AppData/Local/Temp/text-placeholder.png)

## Editor

Use **Editor** when the designer needs more space to write or format content.

This is useful for longer text blocks such as:

* descriptions
* rich content sections
* notes or instructions
* formatted text with paragraphs and structure

If a normal text field feels too small, **Editor** is usually the better choice.

![Editor Placeholder](C:/Users/amirt/AppData/Local/Temp/editor-placeholder.png)

## Yes/No

Use **Yes/No** when the designer only needs to turn something on or off.

This is best for simple decisions such as:

* show or hide a feature
* enable or disable a setting
* allow or block a behavior
* turn an option on for one experience

It is the fastest way to control a binary option.

![Yes No Placeholder](C:/Users/amirt/AppData/Local/Temp/yes-no-placeholder.png)

## Select

Use **Select** when the designer must choose one option from a predefined list.

This is useful when only one answer should be active, for example:

* choosing one experience mode
* selecting one category
* picking one currency or one style
* choosing one configuration option

It keeps the experience clean because the designer only picks one valid value.

![Select Placeholder](C:/Users/amirt/AppData/Local/Temp/select-placeholder.png)

## Multi

Use **Multi** when the designer should be able to choose more than one option.

This is useful for cases like:

* selecting multiple tags
* choosing several features
* assigning more than one style or category
* enabling several related options at the same time

If **Select** is for one choice, **Multi** is for many choices.

![Multi Placeholder](C:/Users/amirt/AppData/Local/Temp/multi-placeholder.png)

## Uploader

Use **Uploader** when the designer needs to add a file, image, or attachment.

This can be used for:

* product images
* cover images
* supporting files
* media assets
* extra documents connected to the experience

It is the right choice any time the designer needs to bring external files into the experience.

![Uploader Placeholder](C:/Users/amirt/AppData/Local/Temp/uploader-placeholder.png)

## Date

Use **Date** when the designer needs to choose a date, a time, or both.

This is helpful for:

* event timing
* publishing schedules
* booking-related inputs
* expiration dates
* start and end moments for offers or settings

It gives a clear and structured way to work with time-based information.

![Date Placeholder](C:/Users/amirt/AppData/Local/Temp/date-placeholder.png)

## When to use this group

These input types are best when the designer wants to make quick updates without opening a large advanced structure.

They are small building blocks, but they are used all the time across different experience types.