Github REALLY needs this markdown improvment

[CorgiMasterEpic]

Select Topic Area

Question

Body

GitHub really, really, really needs a Markdown update…

It’s starting to become a real problem.

---

Problem 1: Backquotes on GitHub vs. VS Code

Backticks (code) & Backqoutes ("> ") look so much better in VS Code.

Open a Markdown file in VS Code, type a blockquote or code block, and compare it to how GitHub renders it.

This does not look the same as VS Code…

fn main() {
    println!("Neither does this...");
}

VS Code’s preview feels clean, modern, and readable.
GitHub’s Markdown rendering feels cramped, outdated, and inconsistent.

And this is more than just backquotes that’s just the biggest difference in my opinion.

I personally think this is the big one.

---

Problem 2: No syntax highlighting while editing READMEs

Nearly every modern editor supports inline syntax highlighting in Markdown.
GitHub still doesn’t.

This makes large READMEs far harder to work with than they should be.

---

Problem 3: Blocking custom CSS is… unnecessarily restrictive

Imagine the possibilities if GitHub even allowed basic styling.
Custom themes, better spacing, improved typography, tons of potential completely blocked.

---

If GitHub ever updates their Markdown engine, it’ll be a miracle.

Everything else already has these features…

I probably would not notice if they just ripped it from vs code it looks so sad 😐

---

[SoloShown]

I completely agree with your points — GitHub’s Markdown experience really feels outdated compared to modern editors.

1. Rendering differences (VS Code vs GitHub)
   VS Code’s Markdown preview is clean, well-spaced, and visually consistent. GitHub’s rendering often looks cramped or less polished, especially with blockquotes and code blocks. The inconsistency between writing in VS Code and viewing it on GitHub is definitely noticeable.

2. No inline syntax highlighting while editing
   This is a big limitation. Almost every serious Markdown editor now supports syntax highlighting inside fenced code blocks during editing. GitHub not having this makes long README files much harder to maintain, especially for projects with a lot of documentation.

3. No custom CSS
   While I understand why GitHub restricts custom CSS (security, branding consistency, etc.), even allowing a limited set of safe styling options would massively improve readability and customization. It would open the door to better typography, spacing, and theme options without harming the platform.

Overall, GitHub is far behind the tools developers actually use every day. A modern revamp of their Markdown engine would make a huge difference, and many of us would welcome it.