[CONTEDIT-52] Visual design for embeds (i.e. tweets, youtube, etc) in Editor Created: 16/Mar/17  Updated: 08/Sep/17  Resolved: 23/May/17

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

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Anja von Gunten
Resolution: Duplicate Votes: 0
Labels: to-specify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Four resource types of oembed.png    
Issue Links:
Relates
causality
caused by CONTEDIT-14 Embed content from other website in t... Closed
caused by CONTEDIT-15 Embed video in the article story 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:
Epic Link: Content Editor fine-tuning

 Description   

We've implemented embeds as part of ARTEDIT-14 and ARTEDIT-15, but the content returned is currently not styled.

Visual design needs rework

We've originally assumed (see ARTEDIT-14) that the visual appearance of embedded content was given by the library actually implementing the embed. Our implementation, however, works differently: we retrieve structured content which we then have to style ourselves.

We thus have develop styles for four "resource types" defined by the oEmbed convention ourselves. The resource types and the parameters they come with are shown below.

Four resource types of oEmbed

Goal

  • We show how the four resource types of oEmbed ("photo", "video", "rich" and "link") look and work in the content editor UI.
  • We also define how they look and work in the default templates delivered by the article editor module.


 Comments   
Comment by Anja von Gunten [ 23/May/17 ]

This issue is covered by
https://jira.magnolia-cms.com/browse/CONTEDIT-73

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