<div dir="ltr">Hi,<div><br></div><div>As you said perhaps it does not exist and I think it doesn't. They should realise that they need a bespoke CMS. I would suggest to create an open source project and make the CMS public so it could become, in the near future, an Open source JSON CMS :-) </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 11 September 2013 10:31, Ian Kynnersley <span dir="ltr"><<a href="mailto:iankynnersley@gmail.com" target="_blank">iankynnersley@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for all the useful responses. I'll definitely look into Active Model Serializer. <div><br></div>
<div>Most of these replies rely on me creating a bespoke model structure in code which is what I'm trying to avoid. Parse and Helios look interesting but don't give me the admin interface that I need to allow totally non-techie users to be able to manage the content themselves.</div>
<div><br></div><div>What I'm after would be a library that I can install in my app (or something hosted like Parse / Helios) that instantly gives me my CMS. Something a bit like Radiant maybe. I would then want to create my model structure within that CMS such that admin users could add, remove and update information easily. However, unlike a normal CMS which would render the output as a website with some templates to alter the look and feel, I want it to provide a JSON API. </div>
<div><br></div><div>The reason for all of this is that ownership of this app will be handed over to a different company and they are (rightly) nervous about taking on a completely bespoke application rather than a customised version of an off-the-shelf product.</div>
<div><br></div><div>Perhaps I am looking for something that doesn't exist so your thoughts are all very useful.</div><div><br></div><div>Thanks again</div><span class="HOEnZb"><font color="#888888"><div>Ian</div></font></span></div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">
On Wed, Sep 11, 2013 at 3:20 AM, Tejas Dinkar <span dir="ltr"><<a href="mailto:tejasdinkar@gmail.com" target="_blank">tejasdinkar@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div style="word-wrap:break-word"><div><div><div>On Sep-11-2013, at 7:02 AM, Nick Novitski <<a href="mailto:nicknovitski@gmail.com" target="_blank">nicknovitski@gmail.com</a>> wrote:</div><blockquote type="cite">
<div dir="ltr" style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
There's also<span> </span><a href="https://github.com/rails-api/active_model_serializers" target="_blank">https://github.com/rails-api/active_model_serializers</a> </div></blockquote></div><div><br></div></div>+1 on Active Model Serializer.<div>
<br></div><div>Benefits:</div><div>1) Easily testable, and OO</div><div>2) Has access to current_user (or any other controller method via `scope'). This makes it possible for you to serialize based on who has requested the object</div>
<div>3) Works seamlessly with respond_with </div><div>4) If you have the same relation object multiple times on your object (say user can be created_by, updated_by, etc…) then you have a way to just `embed' the user once.</div>
<div><br></div><div>Also, +1 on rails-api gem as well :-)</div><div><div>
--<br>Tejas Dinkar<br><a href="http://www.nilenso.com" target="_blank">http://www.nilenso.com</a><br>Nilenso Software (formerly C42 Engineering)<br>
</div>
<br></div></div><br></div></div><div class="im">_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></div></blockquote></div><div class="im"><br><br clear="all"><div><br></div>-- <br>
<br>Ian Kynnersley<br><a href="http://iankynnersley.co.uk" target="_blank">http://iankynnersley.co.uk</a> | <a href="tel:%2B44%20%280%29%207973%20420%20829" value="+447973420829" target="_blank">+44 (0) 7973 420 829</a> | <a href="http://twitter.com/kpopper" target="_blank">http://twitter.com/kpopper</a>
</div></div>
<br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Riccardo Tacconi<br>Ruby on Rails and PHP development - System Administration<br><a href="http://www.virtuelogic.net/" target="_blank">VIRTUELOGIC LIMITED</a><br>
<br><a href="http://github.com/rtacconi" target="_blank">http://github.com/rtacconi</a><br><a href="http://riccardotacconi.blogspot.com" target="_blank">http://riccardotacconi.blogspot.com</a><br><a href="http://twitter.com/rtacconi" target="_blank">http://twitter.com/rtacconi</a>
</div>