Proof read and checked links for the neovim post. Ready to post.
This commit is contained in:
@ -142,6 +142,20 @@ if (!doNotTrack) {
|
||||
</footer>
|
||||
</article>
|
||||
|
||||
<article class="post-entry">
|
||||
<figure class="entry-cover"><img loading="lazy" src="./neovim-to-neovim-mini.png" alt="Large Neovim logo, partly out of frame with a chalk arrow pointing to a smaller neovim logo with the word 'mini'.">
|
||||
</figure>
|
||||
<header class="entry-header">
|
||||
<h2>Mini Neovim
|
||||
</h2>
|
||||
</header>
|
||||
<div class="entry-content">
|
||||
<p>If I’m being honest, when I started this quick project to reduce my Neovim plugin footprint size, I thought I was going to be able to get rid of way more plugins! Inspired by this Reddit post that setup a Neovim config using only echasnovski’s mini library, I was reminded that some of my remote server environments were still using Packer as their plugin manager, where my main machine has upgraded to Lazy....</p>
|
||||
</div>
|
||||
<footer class="entry-footer"><span title='2023-10-20 18:38:13 -0400 EDT'>October 20, 2023</span> · 3 min · 602 words · Me</footer>
|
||||
<a class="entry-link" aria-label="post link to Mini Neovim" href="./posts/mini_neovim.html"></a>
|
||||
</article>
|
||||
|
||||
<article class="post-entry">
|
||||
<figure class="entry-cover"><img loading="lazy" src="./esp_medicine_indicator.png" alt="ESP8266 Logo with a Medicine Icon, Colorized">
|
||||
</figure>
|
||||
@ -230,20 +244,12 @@ To give clear instructions to help users migrate from using Nginx Proxy Manager
|
||||
<footer class="entry-footer"><span title='2023-08-05 15:23:51 -0500 -0500'>August 5, 2023</span> · 8 min · 1635 words · Me</footer>
|
||||
<a class="entry-link" aria-label="post link to Tutorial: Move from NginxProxyManager to Nginx" href="./posts/npm_to_nginx_tutorial.html"></a>
|
||||
</article>
|
||||
|
||||
<article class="post-entry">
|
||||
<figure class="entry-cover"><img loading="lazy" src="./merged-pr-accepted.png" alt="Git Pull Request with an arrow pointing to a check mark">
|
||||
</figure>
|
||||
<header class="entry-header">
|
||||
<h2>My First Merged PR!
|
||||
</h2>
|
||||
</header>
|
||||
<div class="entry-content">
|
||||
<p>Admittedly, I feel a bit like a child sharing something like this, as there are so many devs that pull and merge requests from contributors on a regular basis. However, while I’ve contributed to documentation and/or tutorials and other non-coding portions of repositories, I feel a tiny bit proud that this was the first instance where I was using a library, found a bug, created an issue, cloned the repo to my local machine, found and fixed the code, and opened a pull request....</p>
|
||||
</div>
|
||||
<footer class="entry-footer"><span title='2022-09-01 13:25:02 -0400 EDT'>September 1, 2022</span> · 2 min · 328 words · Me</footer>
|
||||
<a class="entry-link" aria-label="post link to My First Merged PR!" href="./posts/whiptail-first-merged-pr.html"></a>
|
||||
</article>
|
||||
<footer class="page-footer">
|
||||
<nav class="pagination">
|
||||
<a class="next" href="./page/2.html">Next »
|
||||
</a>
|
||||
</nav>
|
||||
</footer>
|
||||
</main>
|
||||
|
||||
<footer class="footer">
|
||||
|
||||
Reference in New Issue
Block a user