<?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: Kawai</title>
    <description>The latest articles on DEV Community by Kawai (@crafty).</description>
    <link>https://dev.to/crafty</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%2F599331%2F8b16c5e0-0259-4430-9006-4c83f82a7612.jpeg</url>
      <title>DEV Community: Kawai</title>
      <link>https://dev.to/crafty</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/crafty"/>
    <language>en</language>
    <item>
      <title>Create Our Dev 🐸</title>
      <dc:creator>Kawai</dc:creator>
      <pubDate>Thu, 18 Mar 2021 16:53:43 +0000</pubDate>
      <link>https://dev.to/crafty/create-our-dev-5b4f</link>
      <guid>https://dev.to/crafty/create-our-dev-5b4f</guid>
      <description>&lt;h1&gt;
  
  
  This is the Main Title
&lt;/h1&gt;




&lt;p&gt;Markdown allows us to write HTML in a quick and fluid way. We use this on the regular for our code reviews, comment sections and README files again and again. &lt;/p&gt;

&lt;p&gt;At first glance the importance of Markdown may not seem all that important. You would be right wrong! Readability in your PRs and being able to communicate your point clearly and cleanly is crucial. Its not uncommon for engineers to create documents ahead of time to their team members for future features on apps that support Markdown to get their point across!&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;List Item&lt;/li&gt;
&lt;li&gt;List Item

&lt;ol&gt;
&lt;li&gt;List Sublist 1&lt;/li&gt;
&lt;li&gt;List Sublist 2&lt;/li&gt;
&lt;/ol&gt;


&lt;/li&gt;
&lt;li&gt;LIst Item 3&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Challenge: 2nd Paragraph
&lt;/h2&gt;

&lt;h5&gt;
  
  
  Step 1
&lt;/h5&gt;

&lt;blockquote&gt;
&lt;p&gt;"Add a 2nd paragraph to your article."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h5&gt;
  
  
  Step 2
&lt;/h5&gt;

&lt;p&gt;&lt;strong&gt;Bold something&lt;/strong&gt; in either paragraphs.&lt;/p&gt;

&lt;h5&gt;
  
  
  Step 3
&lt;/h5&gt;

&lt;p&gt;&lt;em&gt;Italicize&lt;/em&gt; something in either paragraphs.&lt;/p&gt;

&lt;h5&gt;
  
  
  Step 4
&lt;/h5&gt;

&lt;p&gt;&lt;del&gt;Strikethrough&lt;/del&gt; something in either paragraphs.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Learning Markdown 🐸</title>
      <dc:creator>Kawai</dc:creator>
      <pubDate>Thu, 18 Mar 2021 16:52:05 +0000</pubDate>
      <link>https://dev.to/crafty/learning-markdown-51pl</link>
      <guid>https://dev.to/crafty/learning-markdown-51pl</guid>
      <description>&lt;p&gt;Test post&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
