> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/publishing-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/publishing-docs/publishing-options/listing.md).

# Listing

## **What is a Listing?**

**A listing is the content preview that users see on the app.** The content name and description is presented along with media that you add in [Themes & Assets](/publishing-docs/publishing-options/theme-and-assets.md).

## How do I create a Listing?

When setting up the listing, the following details can be added:

* **Name.** Up to 128 characters
* **Feature / Promotional Text.** A short summary of your content (73 / 128 characters).
* **Full Description.**  Long description of your content.
* **Estimated Duration Days.** [*Pathways*](https://everyday-digital.gitbook.io/pathways-docs/) *only.* Estimated days and hours required to complete the Pathway. 
* **Category.** Choose or add a content category that will be visible to app users (you can create different categories for [Streams](https://everyday-digital.gitbook.io/streams-docs/) and [Learning Stories](https://everyday-digital.gitbook.io/authoring-docs/authoring/content-types/learning-story)).
* **Tags.** Up to 5 tags (used to optimise the app search).
* **Spoken Language.** Specify which language the content is presented in.
* **Explicit Content.** Declare whether the content is explicit. Choose No (All Ages), Somewhat (16 and Over), or Yes (10 and Over).       

{% hint style="info" %}
If any of your episodes contain **explicit** content, you must set this option to **"Yes"**. If adding from a podcast or from YouTube, **this will automatically be determined**. Even if only one **episode contains explicit** content, you must select "Yes". For more info, please read the YouTube guidelines here [and refer to general podcast guidelines here ](https://www.youtube.com/intl/en-GB/about/policies/#community-guidelines/).
{% endhint %}

### Enable Reviews ([Articles](https://everyday-digital.gitbook.io/authoring-docs/authoring/content-types/article) & [PDF's](https://everyday-digital.gitbook.io/authoring-docs/authoring/content-types/pdf-document))

Choose to enable comments and reviews.

### **Publish to Pathway Only (Experimental)**

* **On.** Content will only available on the Pathway(s) to which it has been added, and will not be available on the Discover section of the app.
* **Off.** Content will be available on the Discover section of the app and on the Pathway(s) to which it has been added.

{% content-ref url="/spaces/uVFZPn6NWEBzyt3Pl8h6" %}
[Authoring](https://everyday-digital.gitbook.io/authoring-docs/)
{% endcontent-ref %}

{% content-ref url="/spaces/UTpgpthx85UKIDy6CNFa" %}
[Pathways](https://everyday-digital.gitbook.io/pathways-docs/)
{% endcontent-ref %}

{% content-ref url="/spaces/B8LkdD0lYdlLcu9BmwI2" %}
[Streams](https://everyday-digital.gitbook.io/streams-docs/)
{% endcontent-ref %}


---

# 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://everyday-digital.gitbook.io/publishing-docs/publishing-options/listing.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.