Currently, only the basic headline for web site is visible by default for a story. If a story is aimed at ending on the print, it is possible to add a specific headline for the print channel but it is far from being visible to the user.
As a result, it may be forgotten in the process.
As an admin, I would like to be able to decide which headlines are shown by default in the 'Compose' tab of a story among the available headline types (mobile, native, print, etc.). Each headline is presented along with its planned downstream channel.
Thus, a journalist working on a story for print, would be directly thinking to create a specific print headline if he thinks it is required.
Guillaume Lefebvre
| Categories | Layout |
While this is available in Composer 2.0 and displays on the Planning tab, ideally we would like this to be displayed on the main Compose panel too.
I agree that this would be a big time saver for our newsroom.
We would like the ability to feature whatever headlines we want on the main Compose tab, not hidden away behind a button. And hide all headlines we don't have a use for.
So many headline options are confusing for users, and in the case of our team, they need to scroll right down to the bottom of the list to find the one they want. Can this please be considered for 2023?
Hi,
Journalists are not yet forgetting the secondary headlines because they don't work yet in Composer but I'm convinced they are likely to forget it when they are using Composer. Showing the different secondary headlines used in our organization by default would make it visible for them that they can have alternate headlines depending on the publishing media.
Our story templates are indifferently used for web and print and consequently, and we determine that a template is aimed for print or not.
Eventually, should a change be planned on this item, it would be great that as an organization i can define in the Settings the label given to each secondary headline as translations may not be accurate or the use we make of a secondary headline may not fit to its actual naming.
Hi Lawrence,
My answers to your questions:
Yes, it is a risk that we face because the field is not visible by default and the user has to click on a button (whose label is not very explicit) to see that he can add a headline for print or for a push notification on mobile
When a story is created, you are likely not to know that the story is planned for print. Yet, if you implement a feature where an admin can decide to show or not the secondary headlines, then for my organization I will decide to show for every template the headline for print and for mobile app push notifications
Hi Lawrence,
Indeed my request aims at making sure journalists and editors are aware that they can/must give a specific headline for print or Push Notifications. It is obviously not mandatory to set them but it is also good for people working against the clock that they can immediately see all the capabilities offered by the product.
It would also ease my life if I could reorder the different types of headlines as I want and change the label that defines their purpose as it can be customer specific.
In terms of layout, you can imagine that the main headline remains presented as it is today but that there is a specific block in the Compose tab listing the different headlines I would like to see used by journalists (based on a parameter setting of Composer) with the labels I wanted to have.
I hope it clarifies.
Hi Guillaume, thank you for your idea submission! Have a question for you as I try to understand your workflow:
Sounds like the problem is some of your users are forgetting to input a headline for "print" headline field, since it is not apparent or required?
Thus, a journalist working on a story for print, would be directly thinking to create a specific print headline if he thinks it is required. - when your journalists work on a story for print, do they work off of a template you've created?
Thanks!