---
title: "Designing a digital project: A reference scenario"
slug: "designing-a-digital-project-a-reference-scenario"
updated: 2025-09-01T10:11:04Z
published: 2025-09-01T10:11:04Z
canonical: "documentation.deltatre.com/designing-a-digital-project-a-reference-scenario"
---

> ## 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.

# Designing a digital project: A reference scenario

In this article, we cover the main digital producers responsibilities and the reference scenario we use to show how FORGE helps them.

---

## Digital producers responsibilities

Digital producers are responsible for:

- Overseeing the editorial team by making sure they have access to what they need to create and manage content
- Designing how your audience consumes the content created by the editorial team by:
  - Designing how to present it.
  - Make sure the reusability of the presentation building blocks and the efficiency in maintaining the design itself.
- Controlling the evolution of the content and presentation of your digital product.

## FORGE Page Builder

The front-end is what your end users experience. As a producer, use FORGE Page Builder to design websites and apps to create a clean and intuitive user experience.

FORGE Page Builder is the design tool to craft the front-end information architecture, regardless of the channel (web, app, etc.) and technology.

## A reference scenario

The following sections show how FORGE manages the presentation of a digital product by designing a *reference scenario. It's* a simple sample project that the articles develop to exemplify what FORGE offers to craft the presentation of digital content.

The goal is to manage the *A big fan of Alpha* project that has to deliver a website and a mobile app:

- The website of Club Alpha: *www.alphaweb.net*
- The mobile app of Club Alpha: *AlphaApp*

> [!NOTE]
> **Note:** The site, *www.alphaweb.net* and the app *AlphaApp* are just names for the reference scenario example.

You need to face two macro tasks:

1. Design: Oversee the presentation of both channels.
2. Permissions: Assign some editors to the website and others to the app.

In the following articles, we'll explore the design in-depth and leave the permissions task to the section dedicated to ‌administrator features.