Automated deployment: Thu Jun 24 05:13:58 UTC 2021 c4c1020aa0

en/awesome-plugins.html

@@ -161,7 +161,11 @@
 <li><a href="https://github.com/sayanarijit/material-landscape2.xplr">material-landscape2.xplr</a></li>
 </ul>
 <h2 id="integration"><a class="header" href="#integration">Integration</a></h2>
-<p>foo</p>
+<ul>
+<li><a href="https://github.com/sayanarijit/dua-cli.xplr">dua-cli.xplr</a>
+Get the disk usage using <a href="https://github.com/Byron/dua-cli">dua-cli</a> with
+selection support.</li>
+</ul>
 
                     </main>
 

en/print.html

@@ -1310,7 +1310,7 @@ end
 return { setup = setup }
 </code></pre>
 <h2 id="publishing"><a class="header" href="#publishing">Publishing</a></h2>
-<p>When publishing plugins to GitHub or other repositories, it's a best practice
+<p>When publishing plugins on GitHub or other repositories, it's a best practice
 to append <code>.xplr</code> to the name to make them distinguishable. Similar to the
 <code>*.nvim</code> naming convention for <a href="https://neovim.io">Neovim</a> plugins.</p>
 <h2 id="examples"><a class="header" href="#examples">Examples</a></h2>
@@ -1327,7 +1327,11 @@ to append <code>.xplr</code> to the name to make them distinguishable. Similar t
 <li><a href="https://github.com/sayanarijit/material-landscape2.xplr">material-landscape2.xplr</a></li>
 </ul>
 <h2 id="integration"><a class="header" href="#integration">Integration</a></h2>
-<p>foo</p>
+<ul>
+<li><a href="https://github.com/sayanarijit/dua-cli.xplr">dua-cli.xplr</a>
+Get the disk usage using <a href="https://github.com/Byron/dua-cli">dua-cli</a> with
+selection support.</li>
+</ul>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="todo"><a class="header" href="#todo">TODO</a></h1>
 <ul>
 <li><input disabled="" type="checkbox" checked=""/>

en/writing-plugins.html

@@ -178,7 +178,7 @@ end
 return { setup = setup }
 </code></pre>
 <h2 id="publishing"><a class="header" href="#publishing">Publishing</a></h2>
-<p>When publishing plugins to GitHub or other repositories, it's a best practice
+<p>When publishing plugins on GitHub or other repositories, it's a best practice
 to append <code>.xplr</code> to the name to make them distinguishable. Similar to the
 <code>*.nvim</code> naming convention for <a href="https://neovim.io">Neovim</a> plugins.</p>
 <h2 id="examples"><a class="header" href="#examples">Examples</a></h2>