<?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: olanite azeez</title>
    <description>The latest articles on DEV Community by olanite azeez (@olanite_azeez).</description>
    <link>https://dev.to/olanite_azeez</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%2F3603046%2F009ce97a-15a1-4ffa-ae89-adeb19f9915a.png</url>
      <title>DEV Community: olanite azeez</title>
      <link>https://dev.to/olanite_azeez</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/olanite_azeez"/>
    <language>en</language>
    <item>
      <title>How to use github as a writer or creator</title>
      <dc:creator>olanite azeez</dc:creator>
      <pubDate>Mon, 10 Nov 2025 08:53:16 +0000</pubDate>
      <link>https://dev.to/olanite_azeez/how-to-use-github-as-a-writer-or-creator-37bn</link>
      <guid>https://dev.to/olanite_azeez/how-to-use-github-as-a-writer-or-creator-37bn</guid>
      <description>&lt;p&gt;github is often associated with coding, yet it is a powerful tool for writers and creators. it helps manage drafts, organise resources, and collaborate smoothly with clients or teams.&lt;/p&gt;

&lt;p&gt;version control is one of its strongest features. every change is tracked. you can compare edits, review revisions, and restore original versions without losing work. this makes writing safer and more efficient.&lt;/p&gt;

&lt;p&gt;collaboration becomes more structured through pull requests and comments. writers working with editors or technical teams can share drafts, receive feedback, and manage revisions in a controlled environment. this improves transparency and accountability.&lt;/p&gt;

&lt;p&gt;github helps you organise your portfolio. you can create folders for your articles, scripts, guides, or research notes. you can keep everything tidy and accessible. for more visibility, you can activate github pages and host a simple site where your work is displayed.&lt;/p&gt;

&lt;p&gt;writers can even contribute to open source documentation. many projects need help improving their guides, tutorials, and user documentation. contributing builds credibility and expands your presence in tech communities.&lt;/p&gt;

&lt;p&gt;github is more than a developer platform. it is a professional space where writers can manage their creative process, track progress, and showcase their work with confidence.&lt;/p&gt;

&lt;h1&gt;
  
  
  github #technicalwriting #writingcommunity #contentcreation #opensource #docs #devcommunity #productivity #portfolio #githubpages #techwriting #writersintech #developers #creators
&lt;/h1&gt;

</description>
      <category>writing</category>
      <category>productivity</category>
      <category>tutorial</category>
      <category>github</category>
    </item>
    <item>
      <title>why developers should care about readable documentation</title>
      <dc:creator>olanite azeez</dc:creator>
      <pubDate>Mon, 10 Nov 2025 08:49:25 +0000</pubDate>
      <link>https://dev.to/olanite_azeez/why-developers-should-care-about-readable-documentation-28mi</link>
      <guid>https://dev.to/olanite_azeez/why-developers-should-care-about-readable-documentation-28mi</guid>
      <description>&lt;p&gt;Documentation is more than an afterthought. it is a direct extension of the product itself. when developers treat documentation as a core part of their workflow, the entire team moves faster and the user experience becomes smoother.&lt;/p&gt;

&lt;p&gt;readable documentation lowers cognitive load. when explanations are clear and examples are easy to follow, the reader does not waste time trying to decode intent. they focus on solving the problem rather than interpreting scattered notes. clarity is a productivity tool.&lt;/p&gt;

&lt;p&gt;good documentation strengthens collaboration. every team has different levels of expertise. clearly written information reduces friction and helps new members settle in quickly. it becomes a shared source of truth that supports consistent results across the team.&lt;/p&gt;

&lt;p&gt;well crafted documentation reduces support tickets. when instructions and examples are complete, users spend less time asking repetitive questions. teams spend more time building and improving features instead of providing emergency clarifications.&lt;/p&gt;

&lt;p&gt;readable documentation has simple characteristics. it uses clear headings and subheadings. it explains concepts with real examples. it provides context of why something matters. it is not rushed or vague. it is intentional and structured.&lt;/p&gt;

&lt;p&gt;in the long run, documentation is a developer’s silent partner. treating it as a living part of the project improves speed, accuracy, and user satisfaction.&lt;/p&gt;

</description>
      <category>developer</category>
      <category>productivity</category>
      <category>writing</category>
    </item>
  </channel>
</rss>
