<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Phat Nguyen</title>
    <description>The latest articles on DEV Community by Phat Nguyen (@phat_nguyen_14ee36624a44e).</description>
    <link>https://dev.to/phat_nguyen_14ee36624a44e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1634138%2Fb0834f36-e396-42e9-81c5-b0bb843a0adf.png</url>
      <title>DEV Community: Phat Nguyen</title>
      <link>https://dev.to/phat_nguyen_14ee36624a44e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/phat_nguyen_14ee36624a44e"/>
    <language>en</language>
    <item>
      <title>Solving the Stale Docs Dilemma</title>
      <dc:creator>Phat Nguyen</dc:creator>
      <pubDate>Sun, 16 Jun 2024 11:21:17 +0000</pubDate>
      <link>https://dev.to/phat_nguyen_14ee36624a44e/solving-the-stale-docs-dilemma-38aa</link>
      <guid>https://dev.to/phat_nguyen_14ee36624a44e/solving-the-stale-docs-dilemma-38aa</guid>
      <description>&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F36p5mt9atejj3t8dpzo6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F36p5mt9atejj3t8dpzo6.png" alt="Clarity reminder" width="800" height="697"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hey Dev.to community,&lt;/p&gt;

&lt;p&gt;I've been thinking a lot about the state of our documentation. It's frustrating when important files like &lt;code&gt;README.md&lt;/code&gt;, &lt;code&gt;CHANGELOG.md&lt;/code&gt;, database diagrams, and architectural docs, etc. become outdated because, let's face it, we often forget to update them amidst the hustle of development.&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://clarity.thebase.company/"&gt;Clarity Reminder&lt;/a&gt; out of this pain. Stale docs are a common issue, and I wanted a solution that seamlessly integrates with our workflow to keep our documentation up-to-date without extra effort.&lt;/p&gt;

&lt;p&gt;Clarity Reminder is a GitHub app that nudges you to update essential docs with every pull request. Here’s how it works:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Install the App&lt;/strong&gt;: Add Clarity Reminder to your GitHub repository.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configure&lt;/strong&gt;: Create a &lt;code&gt;.clarity/config.yaml&lt;/code&gt; file to set up custom reminders.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automate&lt;/strong&gt;: The app reminds you to update your docs whenever necessary.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  I Need Your Feedback!
&lt;/h2&gt;

&lt;p&gt;I'm looking for your honest feedback and suggestions. Your input can help make Clarity Reminder better for everyone. Check it out &lt;a href="https://clarity.thebase.company/"&gt;here&lt;/a&gt; and let me know what you think!&lt;/p&gt;

&lt;p&gt;Thanks for reading and happy coding!&lt;/p&gt;




&lt;p&gt;Patrick from The Base Company&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
