We’re working on the post creation experience in daily.dev and need your vote.
Pick the one that feels easiest for you 👇
<hr>
<h3>Option 1️⃣ — Live Markdown</h3>
<ul>
<li>You type with <code>#</code> and <code>**</code> and see the formatting as you write</li>
<li>All-in-one view</li>
<li>No tab switching</li>
<li>Great for pop-ups — the layout stays stable</li>
</ul>
<h3>Option 2️⃣ — Markdown + Preview Tabs</h3>
<ul>
<li>You type using <code>#</code> and <code>**</code>, but see the result only when you click Preview</li>
<li>Two tabs: one to write, one to preview</li>
<li>Cleaner writing space</li>
<li>Ideal for full page (May jump in height when switching views in pop-ups)</li>
</ul>
<hr>
🗳️ Which one feels better for your writing style?
1️⃣ for Option 1 — Live Markdown 
2️⃣ for Option 2 — Markdown + Preview
Thanks for helping us build a better writing experience 🙌

Where we talk all things daily.dev. Check out the threads below and share what you love, or tell us what you hate. Can't wait to meet you 🤗

daily.dev World

Daily.dev is seeking community feedback on two markdown writing interface options for their post creation feature. Option 1 offers live markdown rendering where formatting appears as you type, providing an all-in-one view without tab switching. Option 2 uses separate write and preview tabs, offering a cleaner writing space but requiring manual preview switching. The team wants user input to determine which approach better suits developers' writing preferences.

Help Us Decide: What’s Your Ideal Markdown Writing Experience?

I’ve always liked the hybrid version of this. So you write the markdown, you see the change live, but you also still see the <code>#</code> or <code>**</code>
Kind of like how discord handles it:
<img src="https://media.daily.dev/image/upload/s--9nQnB0ax--/f_auto/v1753107592/ugc/content_858f6e4e-3708-4a98-b3ff-4ae647db7a85?_a=BAMClqZW0" alt="image">
Although I don’t like how it doesn’t show the headers or links with a nice rendering

Option 1 might limit readability, markdown standardness and extensibility.
Imo, option 2 is simpler (and therefore in most cases better) because there are already thousands of open-source, standard markdown editing libraries out there.
It would also be consistent with Github’s implementation.
A consequence of the “standardness” of option 2 is that it will offer a much wider range of md features than the live version (I find it difficult to imagine writing md tables in a “live” editor without it becoming a nightmare…).

2 is the best and by far in my opinion

2️⃣ - but #1 isn’t bad either as long as it’s not buggy. To me the more important features are keyboard shortcuts for bold/italics and hyperlinks, and being able to paste in large amounts of markdown without losing formatting.

2️⃣
I hate live markdowns but I guess I’m in the minority here.
It’s so confusing to see formatting change when you type, and then you have to change something and you can’t do it properly anymore.