Port Codeigniter App to PyroCMS

I'm working on a web application in Codeigniter. I'd like to integrate the functionality of my application with a CMS so that site admins can easily update the site (about pages, blog, etc). Is this easily done with PyroCMS or another Codeigniter-based CMS? Will I need开发者_运维知识库 to drastically restructure my existing app?

From my own experience integrating an app inside Expression Engine I can say that a CMS changes the way you usually work with CI. So be prepared to make some adjustments. Every CMS will come with it's perks and differences. It shouldn't be a big problem though.

If you want to use PyroCms take a look at this doc first: http://www.pyrocms.com/docs/2.0/developers/creating-custom-modules

If you're looking for alternatives, there are a lot. It seems almost everyone working with CI has made it's own.

Here are a few:

• http://www.ionizecms.com/
• http://www.halogy.com/
• http://codefight.org/
• http://www.getfuelcms.com/

Also make sure you check out CI Bonfire, it's not a CMS but does help you when you start up a new project with a basic admin wrapper, which is sometimes more useful than a CMS:

http://cibonfire.com/

This was answered a year ago and answered well, but my support guy has forwarded me a few emails from users asking about this page.

When people talk about Content Management Systems they often suddenly get the idea of rigid backends where you applications have to follow specific rules. While PyroCMS certainly has a few conventions you are free to build your modules just like they are a CodeIgniter application, on the frontend or the backend.

If you want to use Models, Controllers, Views, REST API's, SOAP, whatever the hell, then you can do that.

But, we also offer some awesome tools to make building modules CRAZY-fast. Hate writing CRUD? Well don't bother. Using the Streams API you can leverage the build in "Custom Data" system we use to rock out chunks of interface for you.

Using PyroCMS for your application is certainly not "hacking it into a CMS", this is the exact use-case it was built for.

If you have an existing application, while you can't "put PyroCMS into your app" you can certainly convert your application to a module easy enough.

The simplest way of doing it is to write your models around the CMS' database. Host the CMS at a subdomain with authentication for your admins. (admin.mysite.com) or something and then use the same database to power your front-end for your site.

• Is it the best approach? Probably not.
• Will it work? Yes.

You will probably find it hard to expand vertically & add new features if you're relying on a 3rd party CMS for data entry & backend.