static-cms/packages/docs/content/docs/beta-features.mdx

---
group: Intro
title: Beta Features
weight: 200
---

<Alert severity="error">Features on this page may be broken or may not function as expected. We are working to test and fix the features as well as update the docs. Use at your own risk.</Alert>

Static CMS runs new functionality in an open beta format from time to time. That means that this functionality is totally available for use, an it might be ready for primetime, but it could break or change without notice.

**Use these features at your own risk.**

## Folder Collections Path

See [Folder Collections Path](/docs/collection-types#folder-collections-path).

## Nested Collections

Seed [Nested Collections](/docs/collection-types#nested-collections).

## Commit Message Templates

You can customize the templates used by Static CMS to generate commit messages by setting the `commit_messages` option under `backend` in your Static CMS `config`.

Template tags wrapped in curly braces will be expanded to include information about the file changed by the commit. For example, `{{path}}` will include the full path to the file changed.

Setting up your Static CMS `config` to recreate the default values would look like this:

<CodeTabs>
```yaml
backend:
  commit_messages:
    create: Create {{collection}} "{{slug}}"
    update: Update {{collection}} "{{slug}}"
    delete: Delete {{collection}} "{{slug}}"
    uploadMedia: Upload "{{path}}"
    deleteMedia: Delete "{{path}}"
```

```js
backend: {
  commit_messages: {
    create: 'Create {{collection}} "{{slug}}"',
    update: 'Update {{collection}} "{{slug}}"',
    delete: 'Delete {{collection}} "{{slug}}"',
    uploadMedia: 'Upload "{{path}}"',
    deleteMedia: 'Delete "{{path}}"',
  },
},
```

</CodeTabs>

Static CMS generates the following commit types:

| Commit type   | When is it triggered?        | Available template tags                                     |
| ------------- | ---------------------------- | ----------------------------------------------------------- |
| `create`      | A new entry is created       | `slug`, `path`, `collection`, `author-login`, `author-name` |
| `update`      | An existing entry is changed | `slug`, `path`, `collection`, `author-login`, `author-name` |
| `delete`      | An existing entry is deleted | `slug`, `path`, `collection`, `author-login`, `author-name` |
| `uploadMedia` | A media file is uploaded     | `path`, `author-login`, `author-name`                       |
| `deleteMedia` | A media file is deleted      | `path`, `author-login`, `author-name`                       |

Template tags produce the following output:

- `{{slug}}`: the url-safe filename of the entry changed
- `{{collection}}`: the name of the collection containing the entry changed
- `{{path}}`: the full path to the file changed
- `{{message}}`: the relevant message based on the current change (e.g. the `create` message when an entry is created)
- `{{author-login}}`: the login/username of the author
- `{{author-name}}`: the full name of the author (might be empty based on the user's profile)

## Image widget file size limit

You can set a limit to as what the maximum file size of a file is that users can upload directly into a image field.

Example config:

<CodeTabs>
```yaml
- label: 'Featured Image'
  name: 'thumbnail'
  widget: 'image'
  default: '/uploads/chocolate-dogecoin.jpg'
  media_library:
    config:
      max_file_size: 512000 # in bytes, only for default media library
```

```js
{
  label: 'Featured Image',
  name: 'thumbnail',
  widget: 'image',
  default: '/uploads/chocolate-dogecoin.jpg',
  media_library: {
    config: {
      max_file_size: 512000 // in bytes, only for default media library
    },
  },
},
```

</CodeTabs>

## Summary string template transformations

You can apply transformations on fields in a summary string template using filter notation syntax.

Example config:

<CodeTabs>
```yaml
collections:
  - name: 'posts'
    label: 'Posts'
    folder: '_posts'
    summary: "{{title | upper}} - {{date | date('YYYY-MM-DD')}} - {{body | truncate(20, '***')}}"
    fields:
      - { label: 'Title', name: 'title', widget: 'string' }
      - { label: 'Publish Date', name: 'date', widget: 'datetime' }
      - { label: 'Body', name: 'body', widget: 'markdown' }
```

```js
collections: [
  {
    name: 'posts',
    label: 'Posts',
    folder: '_posts',
    summary: "{{title | upper}} - {{date | date('YYYY-MM-DD')}} - {{body | truncate(20, '***')}}",
    fields: [
      { label: 'Title', name: 'title', widget: 'string' },
      { label: 'Publish Date', name: 'date', widget: 'datetime' },
      { label: 'Body', name: 'body', widget: 'markdown' },
    ],
  },
],
```

</CodeTabs>

The above config will transform the title field to uppercase and format the date field using `YYYY-MM-DD` format.
Available transformations are `upper`, `lower`, `date('<format>')`, `default('defaultValue')`, `ternary('valueForTrue','valueForFalse')` and `truncate(<number>)`/`truncate(<number>, '<string>')`

## Registering to CMS Events

You can execute a function when a specific CMS event occurs.

Example usage:

```javascript
CMS.registerEventListener({
  name: 'prePublish',
  handler: ({ author, entry }) => console.info(JSON.stringify({ author, data: entry.data })),
});
```

Supported events are `prePublish`, `postPublish`, `preSave` and `postSave`. The `preSave` hook can be used to modify the entry data like so:

```javascript
CMS.registerEventListener({
  name: 'preSave',
  handler: ({ entry }) => {
    return entry.data.set('title', 'new title');
  },
});
```