Crafting content with FORGE

This article explains how you can create and manage content in FORGE.

Editor's responsibilities

Staff editors are responsible for writing, editing, and publishing content.

Staff editors typically:

• Complete the content editorial workflow

• Define strategies to promote content once published

• Define relations between content items

• Translate content

• Manage live posts

The FORGE apps you'll likely use daily are:

• FORGE Back Office: The place where content is crafted and published

• LIVE BLOGGING: The place where live blog content is written and delivered

FORGE Back Office

FORGE Back Office is the content manager, the home to all of your editorial work.

The content you manage is organized into entities. Entities, including text, photos, and videos, give ‌structure to the content.

Editorial workflows

Content workflows start from seven different statuses:

• New: Just created entity, not yet edited.

• Unpublished: The entity is not published on the front-end.

• Rejected: A reviewer rejected the request for publishing the edited entity.

• Published: The entity is published on the front-end.

• Reviewed: The entity is published on the front-end and a reviewed version is available to be published.

• Waiting for approval: The entity is ready to be published but requires validation.

• Archived: The entity is unlisted but still available to be restored.

All statuses except New allow you to archive the entity.

Archiving a Published entity

When archiving a Published entity, this becomes unavailable on the front-end.

Starting from New

The only allowed action on a New entity is editing, which moves the status to Unpublished.

Starting from Unpublished

The allowed actions on an Unpublished entity are:

• Send for approval: It requests the approver to publish the entity, which moves the status to Waiting for approval.

• Publish or Schedule publishing: It publishes or schedules publication of the entity on the front-end, which moves the status to Published.

Starting from Rejected

The allowed actions on a Rejected entity are:

• Edit: It moves the status to Unpublished.

• Publish or Schedule publishing: It publishes or schedules publication of the entity on the front-end, which moves the status to Published.

Starting from Published

The allowed actions on a Published entity are:

• Edit: It moves the status to Reviewed.

• Unpublish: It makes the entity unavailable on the front-end, which moves the status to Unpublished.

Starting from Reviewed

The allowed actions on a Reviewed entity are:

• Send for approval: It requests the approver to publish the reviewed version of the entity, which moves the status to Waiting for approval.

• Publish or Schedule publishing: It publishes or schedules publication of the entity on the front-end, which moves the status to Published.

• Unpublish: It makes the entity unavailable on the front-end, which moves the status to Unpublished.

Starting from Waiting for approval

The allowed actions on a Waiting for approval entity are:

• Reject: It moves the status to Rejected.

• Publish or Schedule publishing: It publishes or schedules publication of the entity on the front-end, which moves the status to Published.

Starting from Archived

The allowed actions on an Archived entity are:

• Edit: It doesn’t change the status.

• Restore: It moves the status to Unpublished.

Collaboration

When multiple editors are working on the same entity:

• Every editor can see icons showing which colleagues are editing the entity in the top right corner of the edit page.

  For example, in the screenshot below, Henry TheProducer can see that Michael Content is working on The story of Alpha as well.
  

• When an editor modifies some fields, the other editors see the modified fields highlighted with the same color as the icon of the editor that made changes. Also, a notification of the update displays in the bottom left.
  For example, in the screenshot below, Henry TheProducer can see that Michael Content modified the Title and Slug of the story.
  
  

  Limitations

  No field highlight displays but the notification in the bottom left (e.g., ), when:

  • Editors modify fields in another translation of the entity. For example, Henry TheProducer looks at en-US and Michael Content modifies a field in en-GB.
    

  • When editors modify fields in the General Settings, Context and Tags, Promotion, or Relations sections—regardless of those sections being expanded or collapsed. For example, Michael Content adds a tag.
    

Right-to-Left (RTL) support

Wherever an entity includes text, the selection of an RTL language automatically switches the entity editor into the RTL writing mode.

For example, in the screenshot below, title, headline, and text editor switch into the RTL writing mode due to the Arabic language selection:

FORGE LIVE BLOGGING

FORGE LIVE BLOGGING lets you create and manage live content, including text, images, audio, and video. It lets you engage with final users directly, through which editors have the power to easily manage, produce, and moderate content.

Visit Editing live blog posts page for more information.