<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>ReadMe: Resource Library</provider_name><provider_url>https://readme.com/resources</provider_url><author_name>Sergey Bezdudnyy</author_name><author_url>https://readme.com/resources/author/sergey-auq</author_url><title>7 Unconventional Opportunities to Improve Your API Documentation - ReadMe: Resource Library</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="gYrZ1X98Sc"&gt;&lt;a href="https://readme.com/resources/things-that-dont-seem-like-documentation"&gt;7 Unconventional Opportunities to Improve Your API Documentation&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://readme.com/resources/things-that-dont-seem-like-documentation/embed#?secret=gYrZ1X98Sc" width="600" height="338" title="&#x201C;7 Unconventional Opportunities to Improve Your API Documentation&#x201D; &#x2014; ReadMe: Resource Library" data-secret="gYrZ1X98Sc" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script&gt;
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
//# sourceURL=https://readme.com/resources/wp-includes/js/wp-embed.min.js
&lt;/script&gt;
</html><thumbnail_url>https://readme.com/resources/wp-content/uploads/2024/05/Unconventional-Ways-to-Improve-Docs.png</thumbnail_url><thumbnail_width>200</thumbnail_width><thumbnail_height>200</thumbnail_height><description>When developers think of documentation, we often tend to think of walls of texts or verbose reference guides. However, the purpose of documentation is to be the UI layer for an API or code library: when you&#x2019;re learning something new, documentation is the frontend that you spend most of your time interacting with. At ReadMe, [&hellip;]</description></oembed>
