ebc2471c6b
Prettier formatting our markdown files is causing bugs because of the differences between Gatsby's parser and Prettier's. Also, Prettier formats the inline code-blocks containing example CMS configs, but the formatting it uses doesn't really make much sense or match the suggested CMS config style. It doesn't actually make much sense to format the docs anyway, since we use the CMS itself to edit/generate them.
20 lines
580 B
Markdown
20 lines
580 B
Markdown
---
|
|
label: "File"
|
|
target: file
|
|
---
|
|
|
|
The file widget allows editors to upload a file or select an existing one from the media library. The path to the file will be saved to the field as a string.
|
|
|
|
- **Name:** `file`
|
|
- **UI:** file picker button opens media gallery
|
|
- **Data type:** file path string, based on `media_folder`/`public_folder` configuration
|
|
- **Options:**
|
|
- `default`: accepts a file path string; defaults to null
|
|
- **Example:**
|
|
```yaml
|
|
- label: "Manual PDF"
|
|
name: "manual_pdf"
|
|
widget: "file"
|
|
default: "/uploads/general-manual.pdf"
|
|
```
|