> Are you intending to release the CMS stuff as part of TurboGears? I > know I'd be fairly keen to have a TG-based CMS I could just use on > projects :)
So far my CMS stuff is well packaged inside a single folder. Dump the folder into your project's main directory and add a few hooks - one to your Root controller's __init__() method, one in your project definition to add the database stuf, run a few lines in the tg-admin shell, and you're away. At some point it could quite easily become part of TG - once I finish the modify views for the base elements I'll be posting the results online. > Just a quick thought, but are you intending for the User, Group, Role > classes to be the same as the ones defined in the TurboGears Identity > module? It would be nice to reuse these, especially since you can > customise the Identity model objects... My Account/Group/Role classes have a lot of extra data in them, though I hope to make the interface in the CMS generic enough to handle any valid Identity session.
