Feature update: Rich Content Embeds

#changelog #ux

Hello DEV Community!

I'm excited to announce a significant improvement in how we embed rich content (such as Tweets and Youtube videos) in Forem posts and comments.🎉

Now, you need just the embed keyword and the complete URL of the resource:

{% embed https://... %}

Prior to this change, we embedded rich content by using keywords specific to the type of embed being created. For example, to embed a GitHub repository, we would use the github keyword and the slug to the repository:

{% github forem/forem %}

With our new approach, all you need is the complete URL to the repository:

{% embed https://github.com/forem/forem %}

Our Editor's Guide contains a list of supported content types. Note that embeds that were created using the former approach will still work for now. Eventually, the former approach will be deprecated.

Do jump in and try this new rich-content embed approach out! Please report any bugs you may encounter - thanks!

Originally published on Forem.dev.

Top comments (17)

Michael Tharrington • Feb 17 '22 • Edited

In celebration of this update, I'm gonna embed something here:

I've been really digging this song this AM. 😁👇

🚩 Atul Prajapati 🇮🇳 • Feb 17 '22

oh you just tested this new feature :)

Ben Halpern The DEV Team • Feb 16 '22

Arit, you crushed this.

Arit Developer • Feb 16 '22

Thank you Ben!

Andy Piper • Feb 16 '22

Cool! Thanks for the update! Will we need to update any older content (since the former approach will be deprecated in the future), or will that be handled for us?

Arit Developer • Feb 16 '22

You’re welcome Andy!

Great question! While we have not decided, we will most probably handle the updates of v1 embeds ourselves.

Andy Piper • Feb 18 '22

Do the new embeds have a way to hide the GitHub README to make the embed more compact? In the other Liquid format, it worked to add noreadme to the tag.