# 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:** [7월 1, 2016, 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:** 6

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [7월 2, 2016, 10:02오후 UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723/6 "2016-07-02T22:02:51Z")

</div>

> [@cappslock](#):
>
> how do you know about that route?

I guess mostly because I’ve spent a lot of time here, I’ve read a lot of posts and I’ve read a good number of lines of code.

But also because when I was looking at how post revision history works (note the “raw” button) it could be seen (using the browsers dev tools) that a “raw” route was used.

> [@cappslock](#):
>
> Is there some better API documentation than this topic

Well, I don’t if it’s better. That’s subjective. But there’s this.  
[https://github.com/discourse/discourse\_api](https://github.com/discourse/discourse_api)

---

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