<?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: Rishu Mehra</title>
    <description>The latest articles on DEV Community by Rishu Mehra (@rishumehra).</description>
    <link>https://dev.to/rishumehra</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%2F3074224%2F6fed777c-4563-4311-b81a-4ea565e7e77c.jpeg</url>
      <title>DEV Community: Rishu Mehra</title>
      <link>https://dev.to/rishumehra</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rishumehra"/>
    <language>en</language>
    <item>
      <title>Why Markdown Still Wins in 2025 (Hint: It’s Not Just for Devs)</title>
      <dc:creator>Rishu Mehra</dc:creator>
      <pubDate>Sun, 04 May 2025 11:00:24 +0000</pubDate>
      <link>https://dev.to/rishumehra/why-markdown-still-wins-in-2025-hint-its-not-just-for-devs-2ko5</link>
      <guid>https://dev.to/rishumehra/why-markdown-still-wins-in-2025-hint-its-not-just-for-devs-2ko5</guid>
      <description>&lt;p&gt;Remember when Markdown was just a simple way to write blog posts or README files?&lt;/p&gt;

&lt;p&gt;Fast forward to 2025, and Markdown is doing a lot more than you think.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wait, Markdown Does That Now?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Writers use it to publish newsletters, books, and PDFs&lt;/li&gt;
&lt;li&gt;Developers still love it for docs, changelogs, and GitHub READMEs&lt;/li&gt;
&lt;li&gt;Creators use it inside Notion, Obsidian, Joplin, and even Slack&lt;/li&gt;
&lt;li&gt;And yes, it plays a big role in AI documentation workflows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Turns out, Markdown didn’t just survive—it quietly evolved into one of the most powerful tools for publishing and productivity.&lt;/p&gt;

&lt;h2&gt;
  
  
  But How Did That Happen?
&lt;/h2&gt;

&lt;p&gt;In my new blog post, I break down how Markdown evolved from a plain text syntax to a publishing powerhouse, covering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The original intent of Markdown (and what made it stick)&lt;/li&gt;
&lt;li&gt;The turning point when devs adopted it full-force&lt;/li&gt;
&lt;li&gt;Why writers, creators, and even AI tools use it in 2025&lt;/li&gt;
&lt;li&gt;What Markdown is powering right now that might surprise you&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://www.justmyslide.com/the-evolution-of-markdown-from-plain-text-to-publishing/" rel="noopener noreferrer"&gt;Read the full post here: The Evolution of Markdown — From Plain Text to Publishing&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Markdown is still simple. Still portable. Still clean. But it’s no longer just a dev thing — it’s a publishing engine for the modern internet.&lt;/p&gt;

&lt;p&gt;If you’ve slept on it lately, now’s a great time to see how it fits into your workflow in 2025.&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>webdev</category>
      <category>programming</category>
      <category>documentation</category>
    </item>
    <item>
      <title>Why Dev Teams Wish UX Writers Knew Markdown</title>
      <dc:creator>Rishu Mehra</dc:creator>
      <pubDate>Tue, 22 Apr 2025 07:47:10 +0000</pubDate>
      <link>https://dev.to/rishumehra/why-dev-teams-wish-ux-writers-knew-markdown-43af</link>
      <guid>https://dev.to/rishumehra/why-dev-teams-wish-ux-writers-knew-markdown-43af</guid>
      <description>&lt;h1&gt;
  
  
  How a simple formatting language can bridge the design-dev content gap
&lt;/h1&gt;

&lt;p&gt;As a UX writer, the fastest way to:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Get your microcopy merged without revisions
&lt;/li&gt;
&lt;li&gt;Make PMs stop pinging you about "formatting issues"
&lt;/li&gt;
&lt;li&gt;Keep translations from breaking in production
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;...is to &lt;strong&gt;write in Markdown&lt;/strong&gt;.  &lt;/p&gt;

&lt;p&gt;I recently explained &lt;a href="https://www.justmyslide.com/why-ux-writers-should-learn-markdown/" rel="noopener noreferrer"&gt;why this matters for UX folks&lt;/a&gt;, but here’s what &lt;em&gt;developers&lt;/em&gt; should know:  &lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;3 Ways Markdown Makes Dev Lives Easier&lt;/strong&gt;
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;PRs That Don’t Give You Hives&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;code&gt;.md&lt;/code&gt; files eliminate:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hidden Word/Google Docs formatting
&lt;/li&gt;
&lt;li&gt;"Can you resend this as plain text?" requests
&lt;/li&gt;
&lt;li&gt;Git diff noise from styling changes
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Design System Harmony&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Markdown plays nice with:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Storybook&lt;/li&gt;
&lt;li&gt;Figma plugins&lt;/li&gt;
&lt;li&gt;CMS backends
&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;No more rebuilding UI text from scratch  &lt;/p&gt;
&lt;/blockquote&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Localization That Won’t Break&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Clean syntax = fewer parsing errors in:&lt;br&gt;
&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;   i18n pipelines / Crowdin / Lokalise  
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Free Cheat Sheet:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
I built a &lt;strong&gt;&lt;a href="https://github.com/rishumehra/Markdown-cheat-sheet-for-UX-Writers" rel="noopener noreferrer"&gt;Markdown Cheat Sheet for UX Content&lt;/a&gt;&lt;/strong&gt; with real examples for:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Error messages (&lt;code&gt;!&amp;gt;&lt;/code&gt;)
&lt;/li&gt;
&lt;li&gt;Tooltips (&lt;code&gt;&amp;lt;span class="tooltip"&amp;gt;&lt;/code&gt;)
&lt;/li&gt;
&lt;li&gt;API docs (code block conventions)
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Devs:&lt;/strong&gt; What’s your #1 frustration with UX copy handoffs?&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Writers:&lt;/strong&gt; Want me to cover how to pitch Markdown to your team?  &lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;a href="https://www.justmyslide.com/why-ux-writers-should-learn-markdown/" rel="noopener noreferrer"&gt;Deep dive for UX writers here&lt;/a&gt;&lt;/em&gt;  &lt;/p&gt;

</description>
      <category>ux</category>
      <category>markdown</category>
      <category>devrel</category>
      <category>technicalwriting</category>
    </item>
  </channel>
</rss>
