<p>I think your idea of RSS or JSON would work fine.</p>

<p>The only reason I can think of to use RSS over JSON would be if there was a possibility you wanted RSS readers to be able to consume the content as well.  Otherwise, I'd just stick with JSON and expose it over a web accessible API.</p>

CC BY-SA 3.0
2015-07-14T04:31:32.433Z
2015-07-14T04:31:32.433Z
Brad Bell
<p>We are working on a help guide solution for Craft and our hope is to have all the guide content live in a single master Craft setup and then our client's sites could read and display this content in their admins through a custom plugin.</p>

<p>We have the rough outlines of a proof of concept for it, the missing piece is sharing the content.  We are thinking of using RSS or JSON to do this but wanted to see if there was any other ways we should consider?</p>

CC BY-SA 3.0
2015-07-14T02:40:46.647Z
Is your help guide solution going to be on the same server as your client's or different?
Brad Bell
CC BY-SA 3.0
2015-07-14T02:41:29.370Z
On a different server sadly
Keith Mancuso
CC BY-SA 3.0
2015-07-14T02:53:22.330Z
Does there need to be some authentication/authorization to read the data, or is it public?
Brad Bell
CC BY-SA 3.0
2015-07-14T02:53:43.213Z
It can be public
Keith Mancuso
<entries>
How could I load content from one Craft install into a template of another
# How could I load content from one Craft install into a template of another

(Asked by: username_0 on 2015-07-14)

We are working on a help guide solution for Craft and our hope is to have all the guide content live in a single master Craft setup and then our client's sites could read and display this content in their admins through a custom plugin.

We have the rough outlines of a proof of concept for it, the missing piece is sharing the content. We are thinking of using RSS or JSON to do this but wanted to see if there was any other ways we should consider?

**Tags:** entries
> **Comments:**
> **username_1**: Is your help guide solution going to be on the same server as your client's or different?  
> **username_0**: On a different server sadly  
> **username_1**: Does there need to be some authentication/authorization to read the data, or is it public?  
> **username_0**: It can be public  

---

## 1 answers

### Answer by username_1 on 2015-07-14. Score: 4 | Accepted answer

I think your idea of RSS or JSON would work fine.

The only reason I can think of to use RSS over JSON would be if there was a possibility you wanted RSS readers to be able to consume the content as well. Otherwise, I'd just stick with JSON and expose it over a web accessible API.


---

