Request:
Ability to allow producers to be able to customize a section of shared stories (the main example being stories that our National Content Desk created for our websites). The main purpose of this feature is to allow producers the ability add their own local content to a shared story and still be able to get updates when the primary owner of the content updates the story.
This local content could include:
Each website should be able to choose where they insert the local content to a story.
Multiple websites could define localized content on a shared story, but each should be assigned to website.
Each localized content should only display on the website that created it.
Each website wants the ability to add local content to multiple locations in the story. (These could be pre-determined for the frontend, if needed.)
The content outside of the localized changes should still update when the primary website publishes updates to the story without overriding the localized portion. Example: When a local producer modified a National Content Desk story, we still need the ability for the NCD team to update their content outside of the embed of the story.
When a local producer adds their local content to an NCD story they shouldn't lock the story for the primary website or other local markets wanting to add their own local content as the primary website could be modifying
The story is owned by a different team (national shared desk) and the main part of the text and other embeds created/added by that other team shouldn't be able to be modified.
All updates made by the owner team (shared desk) should be updated for all websites. The link to these updates should not be broken.
Sara Skinner Cole
Here are the fields that our local producers have had the ability to edit on shared stories in the past:
Headline
Sub-headline
Short Headline
Dateline
Media Player (lead media – image, video, livestream)
Author
Topic Keywords (Arc tags)
Primary category (Arc section)
Secondary categories (Arc subsection)
Page redirect URLs
*Producers could add any type of content to the header, middle and bottom of the shared story.
Adding custom tags – Sites need the ability to add their own tags to shared stories. This feature is not in Phase I of the circulation tool in development, but it’s a relatively important need (and has been communicated as such). With more sites launching soon, they are accustomed to adding their own tags to populate their apps.
Headline customization – Sites could tweak headlines as they wished and those tweaks would only display on the site that made the change.
Customization of lead or tease image – Sites could change the tease image that was displayed pages and lists, etc. (Example: This comes up when we’re intensively covering a major topic, such as coronavirus. Local sites’ lists will display several stories showing the same tease image because it’s pulling from the same explainer or evergreen video.)