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 (19)
In celebration of this update, I'm gonna embed something here:
I've been really digging this song this AM. 😁👇
oh you just tested this new feature :)
Arit, you crushed this.
Thank you Ben!
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
noreadmeto the tag.Thank you Andy. Would you please open a ticket for this?
Issue #16673 👍
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?
You’re welcome Andy!
Great question! While we have not decided, we will most probably handle the updates of v1 embeds ourselves.
Very handy! Thanks!
Wait – I already found a bug lol
{% embed https://google.com/ %}doesnt seem to workHello @siddharthshyniben, the link you used is not currently supported.
You can find a list of currently supported embeds here: dev.to/p/editor_guide#liquidtags
Ooooh coooool 🥳🥳🥳
Hey Arit,
This is brilliant! Thanks for letting us know. Now, all I have to do is find a way to get it into my next post ;)
Thanks for the information!
But what does this mean for user privacy? Won't this enable these companies to do cross-site tracking?
At present, the only embeds you can use are the previous embeds; we've just squashed them into a unified syntax. So this has been a privacy neutral change.
are we going to be reading about this as a security vulnerability in a few months?
What are you seeing as the possible security vulnerability?
At present, the only embeds you can use are the previous embeds. The thing that's changed is you don't need to recall which service you're embedding. We're also working on a fallback (e.g. which would be "render the A-tag you provided" but perhaps more)