Embed All the Things!  🔗 **Source:** [Embed All the Things!](https://pento.net/2026/03/26/embed-all-the-things/) > [!note]+ Document Notes > tags: #wordpress #embedding #opengraph #gutenberg > author: Gary Pendergast > source: pento.net > reference: https://pento.net/2026/03/26/embed-all-the-things/ > date created: 2024-12-19 14:30 > > # 🏷️ Title: Embed All The Things! > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Test OpenGraph Fallback Embed plugin for improved embedding experience #wordpress - [H2] Consider embedding standards beyond oEmbed for content strategy #opengraph - [H3] Evaluate plugin approach vs core feature requests for WordPress projects #plugins ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [OpenGraph Fallback Embed Plugin](https://pento.net/2026/03/26/embed-all-the-things/) - [WordPress oEmbed API](https://developer.wordpress.org/apis/oembed/) ## 📝 Summary - Gary Pendergast released a WordPress plugin that extends embedding beyond oEmbed to include OpenGraph, Twitter Cards, and meta tag fallbacks - The plugin fills a 10+ year gap in WordPress embedding capabilities for sites that don't support oEmbed - It integrates seamlessly with Gutenberg's Embed block as a fallback mechanism - This represents a philosophy of keeping some features as plugins rather than forcing everything into WordPress Core - The solution addresses the modern expectation of rich embed experiences across all websites ## 📖 Main Content WordPress introduced oEmbed API support over a decade ago, focusing on giving site owners maximum control over their embed appearance. While this works well for sites that implement oEmbed, many sites only provide basic metadata through OpenGraph or Twitter Card tags. Gary Pendergast, a longtime WordPress Core developer, created the "OpenGraph Fallback Embed" plugin to address this gap. The plugin operates as a fallback system that activates when WordPress's standard embedding mechanisms fail. It attempts to create rich embeds using OpenGraph tags, Twitter Card metadata, or basic meta descriptions. The plugin exemplifies WordPress's pluggable architecture philosophy - not every feature needs to be in Core. It integrates with Gutenberg's Embed block seamlessly, requiring no additional user interaction once installed. This approach aligns with the modern expectation that any URL should produce some form of rich embed, similar to how platforms like Slack, Discord, and Apple Messages handle link previews. ## 🗒️ Notes #### ⏱️ [N/A] — [H1] WordPress oEmbed API legacy and limitations - Key idea: WordPress has supported oEmbed for over 10 years but this only works for sites that implement oEmbed - Evidence: "The code we wrote back then still runs on tens of millions of WordPress sites every day" #### ⏱️ [N/A] — [H2] OpenGraph as universal fallback standard - Key idea: OpenGraph provides a simpler, more widely adopted standard for basic rich embeds - Evidence: "Sometimes, you just need a card with an image and a description, which is where OpenGraph has similarly stood the test of time" #### ⏱️ [N/A] — [H2] Gutenberg's impact on embedding expectations - Key idea: Gutenberg brought rich content experiences to the editor, raising expectations for embedding - Evidence: "The big change is Gutenberg, of course, which really brought forward the idea that the editor should be a rich content experience" #### ⏱️ [N/A] — [H1] Plugin-first development philosophy - Key idea: Some features work better as plugins rather than core functionality - Evidence: "Even as a long time WordPress Core developer, I don't think everything needs to land in Core" #### ⏱️ [N/A] — [H3] Seamless fallback integration approach - Key idea: The plugin activates only when standard embedding fails, requiring no user intervention - Evidence: "This is a block plugin that tries to avoid you using the block it provides if at all possible!" ## 📚 References - [OpenGraph Protocol](https://ogp.me/) - [Twitter Card Documentation](https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/abouts-cards) - [WordPress Embed Block](https://wordpress.org/support/article/embed-block/) ## 🗣️ Paraphrase - WordPress has supported rich embedding through oEmbed for over a decade, but this only works for sites that implement the oEmbed protocol, leaving gaps for many websites - A new plugin extends WordPress embedding to use OpenGraph, Twitter Cards, and basic meta tags as fallbacks, providing rich embeds for virtually any website - This approach demonstrates that not every feature needs to be built into WordPress Core - sometimes a focused plugin provides better user experience and maintainability ## 📰 Newsletter **Expand Your WordPress Embedding Beyond oEmbed** Great news for content creators! Gary Pendergast has released a clever plugin that finally solves the embedding gap we've all experienced. You know those times when you paste a URL and WordPress just shows a plain link instead of a rich embed? This plugin fixes that by using OpenGraph and Twitter Card data as fallbacks. The "OpenGraph Fallback Embed" plugin works invisibly - install it once and forget about it. It only activates when WordPress's standard embedding fails, then tries multiple fallback methods to create rich cards with images and descriptions. This is particularly valuable for Gutenberg users who expect rich content experiences throughout the editor. Instead of waiting for Core changes, this plugin-first approach gives you immediate benefits while respecting WordPress's modular architecture. **Try it out**: The plugin seamlessly integrates with your existing Embed blocks and requires zero configuration. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Evaluate embedding fallback mechanisms for future WordPress versions - Plugins: Test OpenGraph Fallback Embed plugin compatibility with popular themes - Community: Share embedding best practices for site owners implementing OpenGraph - Documentation: Update embedding documentation to include fallback strategies - Design: Review embed card designs for consistency across fallback methods #### Community - Contributors: Test plugin with various site types and metadata implementations - Maintainers: Consider embedding standards in theme review guidelines - Sponsors: Support development of embedding infrastructure improvements ## 🧪 Hypotheses - Sites with proper OpenGraph implementation will see higher engagement when embedded in WordPress posts - Plugin-based embedding extensions provide better user experience than waiting for core implementation - Fallback embedding systems reduce bounce rates by providing richer content previews - OpenGraph adoption will increase as more platforms implement fallback embedding ### 📊 Methodology - A/B testing comparing embed engagement rates before and after plugin installation - Survey analysis of user satisfaction with embedding experiences across different site types - Performance impact measurement of fallback embedding on page load times ### ❓ Questions - How does fallback embedding performance compare to native oEmbed implementations? - What percentage of websites would benefit from OpenGraph fallback embedding? - Should WordPress Core eventually incorporate similar fallback mechanisms? ### 🔮 Future Research - Cross-platform embedding standards harmonization between WordPress, social media, and messaging platforms - Machine learning approaches to extract meaningful embed data from sites without structured metadata - Performance optimization strategies for large-scale embedding fallback systems ### 💡 Implications - Practice: Content creators can embed virtually any URL with rich previews, improving content quality - Policy: Theme developers should consider embedding display consistency in their designs - Security: Fallback embedding requires careful sanitization of third-party metadata - Education: Training materials should cover embedding best practices beyond just oEmbed - Funding: Investment in embedding infrastructure improvements could benefit the entire WordPress ecosystem ### 🧠 Learning Styles Assessment Reading level estimate: 10th grade #### 👀 Visual learners - Present: Clear explanation of embedding concepts and plugin functionality - Improve: Screenshots showing before/after embedding results, diagram of fallback process #### 🔊 Aural learners - Present: Conversational tone explaining technical concepts - Improve: 3-minute audio summary of embedding evolution and plugin benefits #### 🗣️ Verbal learners - Present: Good definitions of oEmbed, OpenGraph, and Twitter Cards - Improve: Analogies comparing embedding to business card exchanges #### 🧩 Kinesthetic learners - Present: Plugin installation and testing process described - Improve: Step-by-step checklist for testing embedding across different sites #### 🧠 Logical learners - Present: Clear timeline of WordPress embedding evolution - Improve: Decision tree for when different embedding methods activate #### 🧑‍🤝‍🧑 Social learners - Present: Community context around WordPress development philosophy - Improve: Discussion prompts about core vs plugin development tradeoffs #### 🧘‍♀️ Solitary learners - Present: Self-contained explanation of embedding concepts - Improve: Reflection questions about embedding strategy for different site types #### 🌿 Naturalistic learners - Present: Ecosystem thinking about WordPress's pluggable architecture - Improve: Connections to broader web standards evolution ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear headings and logical content structure - Improve: ARIA labels for embed preview examples #### Keyboard navigation - Present: Standard blog post navigation - Improve: Skip links for embedded content sections #### Contrast and readability - Present: Good text contrast on blog layout - Improve: Ensure embedded content maintains contrast standards #### Text resizing and reflow - Present: Responsive blog design - Improve: Test embedded content reflow at 200% zoom #### Media and captions - Present: Text-based content with no media barriers - Improve: Alt text for any embed preview screenshots #### Forms and interactions - Present: Standard comment form accessibility - Improve: Accessible plugin installation instructions #### Standards reference - Meets WCAG 2.2 AA standards for text content ### 🌍 DEIB Assessment #### Cultural breadth - Present: Technical content accessible to global WordPress community - Improve: Examples from diverse website types and regions #### Inclusive language - Present: Clear, jargon-free explanations of technical concepts - Improve: Plain language summary for non-technical users #### Neurodiversity support - Present: Well-structured content with clear headings - Improve: Bullet point summaries for key concepts #### Representation - Present: Technical focus with minimal personal references - Improve: Inclusive examples of different types of websites and use cases #### Psychological safety - Present: Encouraging tone about plugin experimentation - Improve: Clear expectations about plugin installation and testing ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Strong logical progression from WordPress embedding history to current needs - Inductive strength: Good evidence from platform examples (Slack, Discord, Apple Messages) - Causal reasoning: Clear cause-effect relationship between Gutenberg and embedding expectations - Analogical strength: Effective comparison between WordPress and other platform embedding #### Fallacies - No significant logical fallacies identified - Tone remains factual and evidence-based throughout #### Tone of voice - Overall tone: Professional, informative, and encouraging - typical of experienced developer sharing practical solutions ### 🛡️ DARVO Analysis - Deny: No denials or defensive language present - Attack: No attacks on other approaches or developers - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive, solution-focused language throughout ## 🎯 Conclusion Gary Pendergast's OpenGraph Fallback Embed plugin addresses a decade-old gap in WordPress embedding capabilities by providing seamless fallbacks for sites that don't support oEmbed. The plugin exemplifies WordPress's pluggable architecture philosophy, demonstrating that not every feature needs core integration to provide significant user value. For WordPress users, this means virtually any URL can now display rich previews, meeting modern expectations set by social media and messaging platforms. The invisible, fallback-only approach ensures no disruption to existing workflows while dramatically expanding embedding capabilities. This development highlights the ongoing evolution of web content standards and the importance of flexible, extensible solutions in content management systems. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] WordPress embedding evolved beyond oEmbed limitations > [!quote] [Embed All The Things!](https://pento.net/2026/03/26/embed-all-the-things/) by [[Gary Pendergast]] via [[pento.net]]. Published 2026-03-26. Accessed 2024-12-19. > "Sometimes, you just need a card with an image and a description, which is where OpenGraph has similarly stood the test of time." Demonstrates recognition that oEmbed's complexity isn't always necessary for effective embedding experiences. [view highlight](https://pento.net/2026/03/26/embed-all-the-things/#H1) #xref #articleseed ID:rw_001 ### [H2] Plugin-first development philosophy for WordPress features > [!quote] [Embed All The Things!](https://pento.net/2026/03/26/embed-all-the-things/) > "Even as a long time WordPress Core developer, I don't think everything needs to land in Core, sometimes a feature can live as handy little plugin." Shows experienced core developer advocating for modular approach over monolithic core expansion. [view highlight](https://pento.net/2026/03/26/embed-all-the-things/#H2) #xref ID:rw_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Fallback systems improve user experience without disruption - Applies when existing functionality partially meets user needs - References invisible activation only when primary methods fail - Links: [[Progressive Enhancement]] [[User Experience Design]] #### [Z2] OpenGraph provides universal metadata standard for embeds - Scope: Web platforms needing basic rich preview functionality - Context: Alternative to complex oEmbed implementations - Links: [[Web Standards]] [[Content Metadata]] [[Social Media Integration]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Test OpenGraph implementation on personal WordPress sites #fleeting #inbox - [F2] Research Twitter Card vs OpenGraph adoption rates across web #fleeting #inbox - [F3] Document embedding strategy for WordPress project documentation #fleeting #inbox <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Embed All the Things!|Embed All the Things!, pento.net]] ## Highlights - Over 10 years ago, we [introduced the oEmbed API to WordPress](https://make.wordpress.org/core/2015/09/30/feature-plugin-merge-proposal-oembed/), expanding how WordPress handled embedding to cover all WordPress sites. It was an intentional decision to focus on oEmbed at the time: we wanted to focus on the embedding mechanism that would give site owners maximum control over what their embeds looked like. The code we wrote back then still runs on tens of millions of WordPress sites every day. ([View Highlight](https://read.readwise.io/read/01kmv7ag7rg422kfm1ree6gc81)) - Tags: 👻 ai highlighted ## New Highlights added 2026-03-28 at 7:22 PM - Over 10 years ago, we [introduced the oEmbed API to WordPress](https://make.wordpress.org/core/2015/09/30/feature-plugin-merge-proposal-oembed/), expanding how WordPress handled embedding to cover all WordPress sites. It was an intentional decision to focus on oEmbed at the time: we wanted to focus on the embedding mechanism that would give site owners maximum control over what their embeds looked like. The code we wrote back then still runs on tens of millions of WordPress sites every day. ([View Highlight](https://read.readwise.io/read/01kmv7ag7rg422kfm1ree6gc81)) - Tags: 👻 ai highlighted ## New Highlights added 2026-03-28 at 8:22 PM - Over 10 years ago, we [introduced the oEmbed API to WordPress](https://make.wordpress.org/core/2015/09/30/feature-plugin-merge-proposal-oembed/), expanding how WordPress handled embedding to cover all WordPress sites. It was an intentional decision to focus on oEmbed at the time: we wanted to focus on the embedding mechanism that would give site owners maximum control over what their embeds looked like. The code we wrote back then still runs on tens of millions of WordPress sites every day. ([View Highlight](https://read.readwise.io/read/01kmv7ag7rg422kfm1ree6gc81)) - Tags: 👻 ai highlighted