# Working with different needs in raw/cooked content

**URL:** <https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723>\
**Category:** Development\
**Created:** [July 1, 2016, 7:36pm 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:** 3

<div class="post-metadata">

**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:** [July 2, 2016, 8:24pm UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723/3 "2016-07-02T20:24:35Z")

</div>

That’s not totally determined yet, but it’s likely that some content will be rendered dynamically which suggests we won’t want the “cooked” version to be static HTML.

I think what we really want is the ability to control _what_ we’re cooking, since we obviously don’t want to throw away whatever sanitation work is done in the process. In our case, we’d probably want to convert “raw” markdown to “cooked” markdown (with whatever scrubbing/moderation happens in that process left intact).

I don’t know if this is on the roadmap or what the timeline is, but failing that, it would at least be useful to be able to get access to the “raw” submission content. Is this possible?

---

_[View the full topic](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723)._