On Thu, Jan 28, 2010 at 1:58 PM, Haron Media <[email protected]> wrote: > > The problem is I don't want to build a generic CMS. We had one but soon > we realized that trying to make it as generic and flexible as possible > was a waste of time.
I think that's why the other projects have floundered. You can build a CMS the way you like it, but somebody else will want something different, or find it easier to write their own than to customize somebody else's. > So what I have actually is a set of reusable MVC components revolving > around some minimal central framework. Building a new site basically > requires unpacking the component tarball into framework root (each > packaged minding the directory structure), and linking URIs to > controllers. This leaves with basic functionality upon which individual > modifications are made per project. If you distribute it as a Python package, you can give basic instructions on how to manually plug it into a Pylons app. E.g., for the controllers, have a shadow controller in the application that imports the code. For templates, add the directory to the template path (and the package should put all its templates under a uniquely-named subdirectory). For the routing, call a function to add the routes. (Recent versions of Routes have a 'submapper' feature that may come in useful.) Or if you design your package as an autonomous WSGI application, it can be plugged into Pylons and other frameworks as an external application under some URL. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
