[CONTEDIT-175] Tagging blocks for reuse Created: 20/Mar/18  Updated: 04/Apr/23  Resolved: 04/Apr/23

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CONTEDIT-225 Support save content with tags action Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Team: AuthorX

 Description   

Support tagging of individual blocks in a story. This allows the author to designate a particular block as the socially shareable text or as the summary.

Problem: The ability to move blocks around provides great flexibility for authors. But it also makes consuming blocks over REST unpredictable. The "first block" is not necessarily the best summary of the story or the best tweetable moment. Authors have no control over what blocks are used when the story is reused in different channels.

User stories:

As a marketer, I want to tag a block in my story with "social", so that I can define which block a Tweet button or Share-on-LinkedIn button should grab when the story is shared in social channels.

Ask an author, I want to tag a block in my story as "summary", so that I know exactly what content a single-page app that consumes the story over a REST endpoint will use as the summary. Retrieving "the first paragraph" over REST is not always the correct thing to do because another writer may have moved paragraphs around, changing the structure of the story.

Acceptance criteria:

  • I can apply any content tags to a selected block.
  • I can clearly see what tags are applied to blocks.
  • I can consume blocks by tag over REST.


 Comments   
Comment by Laura Delnevo [ 04/Apr/23 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 00:17:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.