> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/authoring-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/authoring-docs/authoring/authoring-faq.md).
# Authoring FAQ
## Which media formats are supported
The below media types and formats are supported.
Media Type
Supported
Audio
.mp3 only (limited to 10MB)
Image
.svg, .jpeg, .png
Video
.mp4 only (limited to 30MB)
## Could Not Upload
If you are trying to upload an audio file (.mp3) and get an **error message** "Could Not Upload", it is possible that your file is labelled .mp3 but is not a true .mp3 file.
Files with an **incorrect mime type (file extension)** can pose a security risk and hence we have a strict protocol to return an error if it is not a true mp3.
When uploading audio files, please ensure that the correct media type is applied to the file. Where .mp3 file extensions are returning the error encountered, we recommend making use of **free online conversion tools** to quickly assign the correct media type.
## "Story Completed" message showing although story not complete
If the "Story Completed" message is showing before the end of a story, you may have added a split page (linked pages) on the last page of a story.
To avoid this issue, remove the split page if it is the last page of a chapter.
## Video not playing audio
If a video (either in [Streams](https://everyday-digital.gitbook.io/streams-docs/) or in a [Video page](/authoring-docs/content-pages/content-page-library/video-cover.md) is not playing audio, you may need to adjust the video codec). All videos need to be saved in **.mp4 format.** The **codec** must be set to **ACC** - not .mp3 (2.0 Channel).
{% hint style="info" %}
If you don't have video editing software and need to change your video's codec, please download and make use of [**Handbrake**](https://handbrake.fr/).
{% endhint %}
## Limited background colours
**When you choose to edit a page background colour, you are presented with a custom colour palette.** These colours work well on retina screens and are designed to look good across devices.
## Image cropping on combined pages
If you have combined an [Image Cover](/authoring-docs/content-pages/content-page-library/image-cover.md) page with another page and need the image to fit onto the page without being cropped, you can adjust the settings as described below.
1. Set the **Image Orientation** to **Auto**
2. Set the **Image Fill** constraint to **Fill Width or Fill Height** (for portrait or landscape images respectively).
## What is the Duration?
**A content listing will include the estimated duration / time it will take to complete a story or pathway.**
We use an API from [readable.io](https://everyday-digital.gitbook.io/authoring-docs/authoring/www.readable.io) which calculates the reading time based on written words (all text, dialogs, assessment questions, etc.). This does not include audio, video, and how long it takes a user to interact with activities.
## **Text / Font Colour not updating**
**If you are having difficulty editing a text or font colour, this could be due to a conflict of applied formatting.** For example, your text is made bold and will not adopt a selected colour. To correct this, first select the text colour, and then make the text bold.
## Video Quality and Video Lag
Videos are an expensive resource to run on devices. Where content is video-heavy, it is recommended to use [Streams](https://everyday-digital.gitbook.io/streams-docs/).
{% hint style="info" %}
As a rule, **videos should be used sparingly** within [Learning Stories](/authoring-docs/authoring/content-types/learning-story.md).
{% endhint %}
When videos are on pages closely together, lagging may increase. This is due to the following reasons:
1. **Pages in a** [**Learning Story**](/authoring-docs/authoring/content-types/learning-story.md) **are loaded into view for the current, previous, and next pages**, allowing for page transitions with gestures. When both the next and previous pages have videos, some lag will likely occur and is dependant on: how busy is the device is, the length of the video on the pages, and if network connections are still busy.
2. **Videos are an expensive resource** as each frame is one image and, generally, 24 images are displayed every second. When page navigation occurs the device needs to animate these frames along with the animation of the page. This works fine if videos are spaced apart.
## How can I filter content types in Authoring?
Story types can be filtered on the [Authoring](/authoring-docs/authoring/start-authoring.md) dashboard page. Select a [Story Type](/authoring-docs/authoring/content-types/learning-story.md) and [Category](https://everyday-digital.gitbook.io/publishing-docs/publishing-options/listing).
**Story Types include:**
* Learning Story
* Article / Microlearning
* PDF Documents
* Assessments
* Surveys
* SCORM
## Could Not Open error
**When content has a high number of videos along with an unstable connection, this can cause a bottleneck** in the main thread and intermittently cause a connection timeout on core content files.
In such instances, you may encounter the following error message: ***Could Not Open** - A file or url needed to run this content was not found. Please try re-accessing this content again.*
**The issue occurs under specific conditions:**
1. Number of videos
2. Network condition
{% hint style="success" %}
**An enhancement patch was created** in November 2025 to address this issue. **Please note:** If content has been published before the enhancement date (2025-11-18 11:03 SAST), you will need to publish an update to inherit the patch. You only need to publish an update to content where this issue has been reported on (not all content).
{% endhint %}
## **How can I add a Story Category?**
**Story Categories can be created in the** [**Listing**](https://everyday-digital.gitbook.io/publishing-docs/publishing-options/listing)**.** Categories are helpful to organise your content, and are also visible to users on the app. In Authoring, you can [filter](#how-can-i-filter-content-types-in-authoring) content to show only specific categories.
## How can I search content?
**A** [**Learning Story**](https://everyday-digital.gitbook.io/authoring-docs/authoring/content-types/learning-story) **can contain searchable content.** Two reliable options are available:
**Add a** [**Resource**](/authoring-docs/content-pages/story-and-page-settings/story-tools-and-options.md#resources)
Insert a downloadable file e.g. in Excel format and attach this as a [Resource](https://everyday-digital.gitbook.io/authoring-docs/content-pages/story-and-page-settings/story-tools-and-options#resources) (you could add a simple [text page](/authoring-docs/content-pages/content-page-library/text.md) instruction into the story to guide the user towards the download).
**Add the content that must be searchable into** [**Text pages**](https://everyday-digital.gitbook.io/authoring-docs/content-pages/content-page-library/text)**.**
In a [Learning Story](https://everyday-digital.gitbook.io/authoring-docs/authoring/content-types/learning-story) you can copy and page lists of plain text that can then be searched from the menu option. You can add content over multiple [Text pages](/authoring-docs/content-pages/content-page-library/text.md) e.g. by category or alphabetically. Use a [non-sequential Chapter setting](/authoring-docs/content-pages/story-and-page-settings/story-settings.md#sequence) for users to skip ahead to the section they want to search in. The Story can appear either in a Pathway or as a standalone content item
---
# 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/authoring-docs/authoring/authoring-faq.md?ask=&goal=
```
`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.