[LRUG] CMS for bespoke API

[George Ornbo]

Depending on the complexity of the client I'd favour something like
Backbone to create the client. If you are talking to a RESTful API it is
pretty straightforward to create a CRUD app presuming your API handles auth
and roles somehow.
On 10 Sep 2013 17:47, "Oto Brglez" <otobrglez at gmail.com> wrote:

> Hey Ian!
>
> I would suggest that you look into this two project...
> - https://parse.com/
> - http://helios.io/
>
> - Oto
>
>
> On Sep 10, 2013, at 6:30 PM, Ian Kynnersley <iankynnersley at gmail.com>
> wrote:
>
> Hi all,
>
> For an upcoming project, I will be creating an API to power some mobile
> apps. The API will be largely read-only in JSON and will need to provide an
> admin interface for non-technical users to manage the data that drives it.
>
> By default, I would probably knock up something bespoke with Rails and
> RailsAdmin. Or maybe a Sinatra equivalent. However, there would be definite
> benefits on this project to building it on an established CMS platform
> rather than completely hand-coded.
>
> Has anyone got any experience of using an existing CMS to create an API
> like this without a "public" web interface.
>
> Is there anything specific I need to consider when using existing CMS
> tools or is it as simple as finding one that allows API-suitable
> authentication (i.e. not forms-based) and then creating JSON templates
> rather than HTML ones?
>
> Thanks for your help!
>
> Ian
>
> --
>
> Ian Kynnersley
> http://iankynnersley.co.uk | +44 (0) 7973 420 829 |
> http://twitter.com/kpopper
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130910/98608a91/attachment.html>