---
title: "FORGE Q2 '25"
slug: "forge-q2-25"
updated: 2025-10-10T15:02:13Z
published: 2025-10-10T15:02:13Z
canonical: "documentation.deltatre.com/forge-q2-25"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.deltatre.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FORGE Q2 '25

## Overview

The FORGE 2025 Q2 release introduces major changes to improve usability, control, and content organization.

In the Content Manager, the new Story Editor has a simple, modern way to create and manage stories. A redesigned Administration Panel centralizes system management with improved navigation. The Permission Management page now provides clearer role assignments and visibility settings for better access control.

In the Page Builder, a special page called Metadata Administration lets you change metadata to help with SEO and content descriptions.

---

## Content Manager

### New Story editor

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21533016563356.png)

In today's digital sports landscape, editorial teams are expected to do more than just write — they craft immersive experiences. The new story editor represents a next-gen content management system (CMS) purpose-built for storytelling in sport. It's not just functional — it's strategic, visual, and multilingual.

For more information, read our articles on [creating](/v1/docs/find-and-create-stories) and [editing](/v1/docs/editing-stories) stories.

### New Administration Panel page

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21533078851612.png)

The sports media world runs on precision. Administrators need control over how content is designed, structured, and organized to help editors craft great stories.

The new Administration Panel streamlines managing the editorial engine under the hood.

For more information, read our article on the [administration panel](/v1/docs/administration-panel).

### New Permission Management page

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21533078855196.png)

The new Permission Management page ensures full transparency and control over user permissions. This page makes it easy and clean to manage editorial roles and content access within the Content Manager.

For more information, read our article on [permissions](/v1/docs/permissions).

### Small changes — but still important

UI/UX improvements:

- A more intuitive experience when selecting date and time
- A friendly confirmation pop-up when publishing content: editors can switch it off when no longer helpful
- An error-proof process when publishing content that guides users to fix issues
- When editing entities, the selected page layout configuration (e.g., expanded or collapsed tabs) is now preserved across sessions
- When editing entities, a new popup page shows a translation status overview of the entity
- New modern UI when importing entities
- A new quick filter (Context) on overview pages

## Page Builder

### New Metadata Administration page

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21533078855836.png)

Metadata is important for defining a website's information structure. It tells users and search engines how content is organized, found, and understood. For example, use of SEO within metadata makes content more visible, improves search rankings, and makes sure that the right content reaches the right people quickly.

With a special interface and guided fields, users can now define metadata easily. This will make sure that all published content is consistent, accurate, and SEO-friendly.

For more information, read our article on [defining metadata](/v1/docs/metadata).

### Small changes — but still important

UI/UX improvements:

- It's now possible to define a set of allowed values for page URL parameters — like {slug} — when they value module, layout, and template properties. E.g., when the allowed values for {slug} are A, B, or C, the front-end logic decides what happens for a non-allowed value like D. For more details, see our article on creating [variables](/v1/docs/create-variables).

---

| ## What's next Want to know what we're working on now, vote on a feature, or tell us what you'd like to see? Visit [our roadmap](https://portal.productboard.com/zxgy7gyg9hgbxe7pdvso8j1z/tabs/34-now). |
| --- |