> For the complete documentation index, see [llms.txt](https://cth-development.gitbook.io/store-elements-for-tebex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cth-development.gitbook.io/store-elements-for-tebex/features/using-short-descriptions.md).

# Using Short Descriptions

Short descriptions let you show compact package copy on Package Grid, Package List and Package Card elements without changing the full package description shown on product pages.

This is useful when your Tebex package description is long, rich or formatted for a full product page, but you want a shorter message on store listings.

### Short description syntax

Add a short description inside your Tebex package description using this format:

```
[short-description]Your short description here.[/short-description]
```

For example:

```
[short-description]A great starter rank with useful perks and extra value.[/short-description]
```

Store Elements for Tebex detects this text and uses it in supported listing elements.

{% hint style="info" %}
This syntax is designed to work inside the Tebex package description editor - make sure you switch the package editor to HTML mode first!
{% endhint %}

### Where short descriptions appear

Short descriptions can appear in:

* Package Grid.
* Package List.
* Package Card.

Short descriptions are not shown on the full Product Page.

### Product page behavior

Product pages are designed to show the full package description from Tebex.

{% hint style="info" %}
Use the short description for listings. Use the rest of the Tebex description for the full product page.
{% endhint %}

### Package Grid behavior

Package Grid supports short descriptions and has them enabled by default.

When enabled:

* The grid shows the short description if one exists.
* The grid shows no description at all if no short description exists.

### Package List behavior

Package List supports short descriptions and has them enabled by default.

When enabled:

* The list shows the short description if one exists.
* If no short description exists, the list falls back to the normal package description.
* The **Package description maximum length** setting applies to normal descriptions only.

{% hint style="info" %}
Package List is more text-friendly than Package Grid, so if you'd like to set slightly 'longer' short descriptions, we'd recommend using the Package List element instead.
{% endhint %}

### Package Card behavior

Package Card supports short descriptions and has them enabled by default.

When enabled:

* The card shows a short description if one exists.
* If no short description exists, no description is shown.

Package Card does not fall back to the full package description.

### Turning short descriptions on or off

In supported element settings, use the short description checkbox.

The setting is enabled by default.

Turn it off if you want the element to ignore short descriptions.

### Recommended length

Keep short descriptions brief.

Good short descriptions are usually one sentence.

Examples:

* `Best for new players who want a useful starter boost.`
* `Includes monthly rewards and priority perks.`
* `A compact bundle of server currency and bonuses.`

Avoid using long paragraphs, large lists or heavy formatting inside the short description tag.

### Formatting recommendations

Short descriptions should be plain text.

Do not place large blocks of HTML, images or embedded content inside the short description tag.

The rest of your Tebex package description can still use rich formatting for the product page.

### Example full package description

```
[short-description]A great starter rank with useful perks and extra value.[/short-description]

Our Starter Rank gives you access to useful in-game perks, bonus rewards and a better store experience.

You get:
- Priority queue access
- Monthly rewards
- Cosmetic extras
```

In listing elements, customers see:

```
A great starter rank with useful perks and extra value.
```

On the product page, customers see the full package details without the shortcode/tag being displayed.

### Troubleshooting short descriptions

If a short description does not appear:

1. Check the opening tag is exactly `[short-description]`.
2. Check the closing tag is exactly `[/short-description]`.
3. Confirm the element has short descriptions enabled.
4. Confirm the package has synced from Tebex.
5. Refresh the Wix Editor or published site.

If the short description appears in the wrong place, check that it is inside the package description for the correct Tebex package.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cth-development.gitbook.io/store-elements-for-tebex/features/using-short-descriptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.