> For the complete documentation index, see [llms.txt](https://docs.themeupstudio.com/travio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themeupstudio.com/travio/rename-taxonomies/theme-settings-name.md).

# Theme Settings Name

## Theme Setting Names

Travio has two theme settings where you enter tag slugs:

* `destinations`
* `experiences`

You can find them in Ghost Admin under the theme settings.

### Recommended choice

Keep the setting names as `destinations` and `experiences`.

This is the safest option for most users.

Even if your visitors see **Places** and **Travel Styles**, the internal settings can still be called `destinations` and `experiences`.

### What to enter in these settings

Enter the slugs of the public Ghost tags that belong to each group.

Example:

```txt
destinations setting: paris,tokyo,bali
experiences setting: hiking,culture,food
```

{% hint style="warning" %}
Do not add spaces around commas.
{% endhint %}

If you rename the visible labels:

```txt
Destinations -> Places
Experiences -> Travel Styles
```

you can still use the same two settings:

```txt
destinations setting: paris,tokyo,bali
experiences setting: hiking,culture,food
```

### Optional: change the setting descriptions

If you want Ghost Admin to describe the settings with your new names, edit:

```txt
package.json
```

Find:

```json
"destinations": {
  "type": "text",
  "description": "Comma separated list of tag slugs for destinations."
},
"experiences": {
  "type": "text",
  "description": "Comma separated list of tag slugs for experiences."
}
```

Change only the `description` text:

```json
"destinations": {
  "type": "text",
  "description": "Comma separated list of tag slugs for places."
},
"experiences": {
  "type": "text",
  "description": "Comma separated list of tag slugs for travel styles."
}
```

Do not rename `"destinations"` or `"experiences"` unless a developer is customizing the theme for you.

### Developer-only option

Renaming the actual setting keys is possible, but it is a developer task.

For example, changing:

```json
"destinations": {}
```

to:

```json
"places": {}
```

requires updating many theme files.

It also creates a new Ghost Admin setting. Any values entered in the old setting will not automatically move to the new setting.

Only do this if you are comfortable editing theme code and testing the full theme afterward.

### Developer reference: files that use `@custom.destinations`

If a developer renames the `destinations` setting key, update references in:

* `archive.hbs`
* `author.hbs`
* `custom-post-hero-background-image.hbs`
* `custom-post-hero-default.hbs`
* `custom-post-hero-gallery.hbs`
* `custom-post-hero-scrolling-mosaic.hbs`
* `custom-post-hero-slider.hbs`
* `custom-post-hero-video.hbs`
* `custom-post-hero-wide-image.hbs`
* `destinations.hbs`
* `index.hbs`
* `partials/cards/card-post.hbs`
* `partials/cards/card-post-wide.hbs`
* `partials/cards/card-post-small.hbs`
* `partials/header.hbs`
* `partials/homepage/section-home-destinations.hbs`
* `partials/homepage/section-home-ribbons.hbs`
* `partials/post/post-hero-background-image.hbs`
* `partials/post/post-hero-default.hbs`
* `partials/post/post-hero-gallery.hbs`
* `partials/post/post-hero-scrolling-mosaic.hbs`
* `partials/post/post-hero-slider.hbs`
* `partials/post/post-hero-video.hbs`
* `partials/tag/layout-custom.hbs`
* `partials/tag/layout-default.hbs`
* `post.hbs`
* `tag.hbs`
* `videos.hbs`

### Developer reference: files that use `@custom.experiences`

If a developer renames the `experiences` setting key, update references in:

* `archive.hbs`
* `author.hbs`
* `experiences.hbs`
* `index.hbs`
* `partials/header.hbs`
* `partials/homepage/hero.hbs`
* `partials/homepage/section-home-experiences.hbs`
* `partials/homepage/section-home-ribbons.hbs`
* `partials/tag/layout-custom.hbs`
* `partials/tag/layout-default.hbs`
* `tag.hbs`
* `videos.hbs`

### Important behavior to understand

Travio gives the first group, currently `destinations`, special visual treatment.

Those tags are:

* Displayed as image chips on post cards and post heroes
* Hidden from the generic tag pill list on post cards
* Used in the special header dropdown and filters

The second group, currently `experiences`, is used in filters, homepage sections, ribbons, hero badges, and index pages.

This means the first group should usually be the one you want to show as prominent chips on posts.

### Build after changing code

If you only edit `.hbs`, `routes.yaml`, `locales/en.json`, or `package.json`, a build step is usually not required.

If you edit files under `assets/js/`, run:

```bash
npm run build
```

Then upload the rebuilt theme ZIP.