# Working with different needs in raw/cooked content **URL:** \ **Category:** Development\ **Created:** [2016 年 7 月 1 日午後 7:36 UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723 "2016-07-01T19:36:07Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![cappslock](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cappslock/32/120789_2.png) [@cappslock](https://meta.discourse.org/u/cappslock)\ **Post date:** [2016 年 7 月 1 日午後 7:36 UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723/1 "2016-07-01T19:36:07Z")
I’m using only the API of Discourse with a custom UI. I want to support some custom Markdown extensions which I’d like the “cooked” content of a post to honor. I think there are probably a few ways to do this: 1. Get Discourse to use a custom Markdown parser 2. When posting, convert the Markdown to HTML before submitting it to the Discourse API 3. Getting access to the “raw” post in addition to the “cooked” post after it’s been submitted 1 won’t work for me if it requires a code change to Discourse, because I’d like to use the hosted version. 2 is fine, but we’re still largely limited by what gets “cooked”. For example, we may want to show some dynamic content. Increasingly I think just getting access to the raw content of the original post (3) is probably what I want. Is there a way to do this? Can “cooking” content be disabled via a setting, or the “raw” content obtained via some API call? --- _[View the full topic](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723)._