# Markdown Quote with Onebox Header

**URL:** <https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258>\
**Category:** Feature\
**Created:** [November 18, 2014, 8:09am UTC](https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258 "2014-11-18T08:09:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buddy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/buddy/32/41024_2.png) [@Buddy](https://meta.discourse.org/u/Buddy)\
**Post date:** [November 18, 2014, 8:09am UTC](https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258/1 "2014-11-18T08:09:16Z")

</div>

Continuing the discussion from [talk.commonmark.org](http://talk.commonmark.org),  
[Irony: This forum doesn't use standard markdown - #5 by sam - Meta - CommonMark Discussion](http://talk.commonmark.org/t/irony-this-forum-doesnt-use-standard-markdown/168/5)

I wanted to suggest that quotes could be handled without an extension to markdown syntax: a new route could be created for quote links, with a special onebox engine that renders that link identical to existing quote box headers with no padding below the onebox, such that the following:

```markdown
http://talk.commonmark.org/quote/sam/168/5
>The number 1 issue with using CommonMark here is lack Discourse specific extensions.

```

would render exactly the same as a quote using the current bbcode syntax does. If the quote were expanded by clicking the chevron however, the full post would show, as it currently does, except it wouldn’t clobber the markdown quote.

I understand that currently, links to posts with restricted visibility do not onebox. Those links, in quote format, could onebox to a quote header with no chevron. By the way, I have found a related problem with quoting restricted visibility posts: [Login to your account - What the Daily WTF?](http://what.thedailywtf.com/t/pm-quote-test/4972)

---

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [November 18, 2014, 9:55pm UTC](https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258/2 "2014-11-18T21:55:17Z")

</div>

Keep in mind that you still have to keep compatibility with existing written text.

---

<div class="post-metadata">

**Author:** ![Buddy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/buddy/32/41024_2.png) [@Buddy](https://meta.discourse.org/u/Buddy)\
**Post date:** [November 18, 2014, 10:47pm UTC](https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258/3 "2014-11-18T22:47:36Z")

</div>

I would expect that, if I am understanding what you mean by compatibility correctly, that the change to standard markdown would be a breaking change, and that a solution could be to add a ‘parser version’ column to posts to identify the posts that should never be rebaked – problems with those posts can be solved by editing, to trigger a fresh bake with the new parser.

---

<div class="post-metadata">

**Author:** ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)\
**Post date:** [December 4, 2025, 11:32am UTC](https://meta.discourse.org/t/markdown-quote-with-onebox-header/22258/4 "2025-12-04T11:32:49Z")

</div>