title: Is the PHP CMS Concrete5 compatible with Backbone and Slim?
body: <p><strong>THE ENVIRONMENT:</strong>  Concrete5 parses the URL to find a page's controller - or tools file, which has no view - and renders it's view.  That's a bit simplistic, but it's the gist.</p>
  
  <p>Because Concrete5 has such a beautiful architecture for handling a large amount of content, I am wanting to use it as a sort of backend mechanism to power a web-app written in backbone.  Backbone requires a RESTful implementation, which I have seen implemented with Slim - a PHP-based RESTful api.  </p>
  
  <p><strong>THE CONFLICT:</strong>  Because Concrete5 parses the URL (to either discover the page's controller [which renders the view] or a tool file [which does not render a view]) it conflicts with the REST implementation of Slim.  This part is true...</p>
  
  <p><strong>THIS PART IS MERELY BELIEF:</strong>  Slim's URLs are faux, used merely to make ajax calls (REST) which Backbone uses upon success.  The browser is prevented from performing it's default action - which means there is no conflict with Concrete5 <em>ONCE YOU ARE ON THE PAGE OF CHOICE.</em> </p>
  
  <p><strong>THE QUESTIONS:</strong> </p>
  
  <p>1). So is the answer merely to create a single_page and simply not render the view?<br>
  2). Once 'not rendered', can I simply proceed with the above beliefs?<br>
  3). Or will I be running into more conflicts than I realize?</p>
  
  <p>Surely, there's a way to enable C5 to have <strong>a page</strong> (not the whole site by setting the global 'C5_ENVIRONMENT_ONLY' variable to 'true') to work with a RESTful api.  </p>
  
  <p>Has anyone else done something similar in some other CMS / Backbone project? </p>
  
  <p>TIA</p>