Would be helpful to decouple FieldFormatters from requiring TypedData field definition. The current solution is a bit hacky.
URL Embed in core - 8.3.x?
Filter, field formatter for URL field, and CKEditor button
Need to complete the module in contrib first
Add support for converting links when pasted into CKEditor
Provide ability to configure embedding options
Entity Browser in core - 8.4.x?
Need inline_entity_form in core first?
We could potentially run a sprint on this at NYC Camp this year
The glue UI to help bring it all together with nice UX - 8.4.x?
As a user, I want embed embedded media by URL in my WYSIWYG (via copy/paste or CKEditor button) so that I can create an enriching experience.
As a user, I want to upload audio and video files to my site and have them show up so that I can create an enriching experience.
We lost our goal being able to re-use field widgets through everything (entity browser & entity embed).
Making a View a field widget for entity reference fields
Need to investigate re-using field widgets and formatters easier without actually having actual fields. Typed Data makes this super difficult in D8.
I still think files are files (make them fieldable), but remote media doesn't need to be represented locally for MVP
I would like to be still involved in architecture, guidance and development, but I feel like my time is limited. I would like to make this my last hurrah to see it in. My current bandwidth to dedicate time is only about 5 hours per week. I need to figure out how I can make client work for Lullabot work with this effort. And family.
Dave RSomething about how the Embed button has been fully abstracted and both Entity Embed and URL embed now require and make extensive use. An upgrade path was created for existing Entity Embed buttons to be converted automatically.
I think it's important to agree upon a syntax early on. "Just URLs" is bound to cause problems, because a URL cannot live on its own in a HTML structure (block vs. inline elements). It'd have to live in a <p> element (and CKEditor would automatically create a <p> element, for example), which is not desirable because a video might want to sit at the same level as other paragraphs and therefore shouldn't be wrapped in a paragraph itself. So, something like <oembed>URL</oembed>, where <oembed> always represents a block-level HTML element. I don't think there are examples of oEmbeds that when rendered result in an inline HTML element?
This isn't really related to what I was thinking for a normalizer - see the below example.
It would be kind of nice if pasting a URL in the WYSIWYG would get converted to the embed code syntax and have a nice preview ala Wordpress.
Wim Leers I think this is the part you'd care about here ^
Basically, if the user pastes an URL in the WYSIWYG like https://www.youtube.com/watch?v=dQw4w9WgXcQ we should be able to turn it into an "embed" using the HTML syntax listed at the first part of the "Embed components" section.