Our Story Editor

Enter the main headline for your story. This field is required and drives much of your search visibility and user engagement.

Used in the story URL. Automatically generated from the title but can be edited for clarity and SEO purposes.

Choose one or more authors who should be credited for this story. These names may be displayed on the story page and used for filtering.

Optional. Enter a location that may be used for geographic categorization.

Select a content classification for the story content such as News, Weather, Sports, etc. This is primarily for use with Doubleclick for Producers, where we may have particular ad campaigns targetted towards certain types of content.

This is also a value (rarely used), in ad targetting. If there are certain ad campaigns that you do not want to appear in association with this story.

Upload an image directly from your computer to include in the story’s media carousel.

Select an existing image asset from the image library.

Choose a video previously added to the video library for use the multimedia carousel.

Attach a new video by pasting in a unique ID from your video provider. Currently we are using ViewNexa, but we can use many different providers.

This short summary appears in search previews, social media cards, and some internal modules. Required for SEO purposes. Also becomes the meta description for search.

Request four SEO-optimized titles for the story content in the window from the latest generation of AI, based on your content history.

Request two SEO-optimized metadescriptions for the story content in the window from the latest generation of AI, specifically taylored to your editorial guidelines.

Categories can be of any type you've created, they can be related to specific real estate in your design or they can be content categories like "sports" or "tech-news". It's really whatever you have created! You can assign a story to more than one category, so it's a many-to-many relationship

You can assign this story to a particular producer, so that it can be retrieved in "about us" panels, or in the authorship section of your story page

You may have a need to have stories that don't actually have a story, they are just a poster image that appears in lists and views of many stories, but when clicked redirect the user to another story (perhaps an advertising affiliate), or even to an outside URL (an advertiser's page). It's a clever way of including more advertising options.

This is a handy on/off flag for designating a story as "sponsored". This can be used to trigger changes in the way the story is viewed, for example adding a "sponsored content" indicator for your viewers, or even changing ad targetting.

Another flag, which changes the way the story appears in your views, in this case causing it to have a target="_blank" attribute, so when it is clicked it opens the destination URL in a new browser tab.

Select a publish time for the story other than the default (now). This is useful for embargoed or pre-scheduled stories.

This is the "not before" date on which the story will begin to be shown publicly in the CMS. It will also be excluded from any outgoing data feeds until that time.

This is the "not after" date on which the story will stop being shown in the CMS, or any outgoing data feeds.

We have a two-step publishing workflow, which assumes that within your organization you would like to have two parties review a story before it is seen publicly. Both parties are "producers" and both parties can perform either step. The second one assumes the role of "peer reviewer". A record is kept of both actions, so there is full responsibilty. The same producer can perform both steps with no hindrance, but if that is agains your comapny policy a visible record will remain of it. This button pushes it forward to the next step, assuming that it will be ready for publicaton upon review

We have a two-step publishing workflow, which assumes that within your organization you would like to have two parties review a story before it is seen publicly. Both parties are "producers" and both parties can perform either step. The second one assumes the role of "peer reviewer". A record is kept of both actions, so there is full responsibilty. The same producer can perform both steps with no hindrance, but if that is agains your comapny policy a visible record will remain of it. This button pushes it forward to the next step, assuming that even after review, it will be held from publication