# Wiki sync plugin

**URL:** https://meta.discourse.org/t/wiki-sync-plugin/48946
**Category:** Development
**Created:** [August 21, 2016, 12:39pm UTC](https://meta.discourse.org/t/wiki-sync-plugin/48946 "2016-08-21T12:39:53Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [August 22, 2016, 10:04am UTC](https://meta.discourse.org/t/wiki-sync-plugin/48946/6 "2016-08-22T10:04:28Z")

</div>

You can see an example of a similar setup here:

> [@Using Discourse as a community-powered wiki](https://meta.discourse.org/t/using-discourse-as-a-community-powered-wiki/43599):
>
> The following is a guest post by Sam Nazarko, CEO and founder of [OSMC.tv](http://OSMC.tv) Are you using Discourse in a novel way? If you’re interested in writing a guest post like this one, please get in touch. In 2014, I started working on a new project, OSMC (Open Source Media Center). OSMC is a free and… This topic is for comments on the original blog entry at: [Using Discourse as a community-powered wiki](http://blog.discourse.org/2016/05/using-discourse-as-a-community-powered-wiki/)

There’s also the [LearnDiscourse experiment](https://meta.discourse.org/t/unofficial-community-docs-learndiscourse-org/31931). You can get an idea of how it worked by reading the [workflow doc](https://github.com/erlend-sh/learndiscourse/blob/gh-pages/about.md). I think @fantasticfears who worked on the learndiscourse prototype ran into the same limitation you did, which is why we settled with

> Your changes will be applied the next time we update [learndiscourse.org](http://learndiscourse.org), which usually happens at least once every week.

You might also run into this problem:

> [@Working with different needs in raw/cooked content](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723):
>
> 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: Get Discourse to use a custom Markdown parser When posting, convert the Markdown to HTML before submitting it to the Discourse API 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, …

---

_[View the full topic](https://meta.discourse.org/t/wiki-sync-plugin/48946)._
