For the last few days I have been preparing to release a new plugin that provides simple content management for Grails. I've built the plugin because I have several sites where it will be useful.
I've decided to opensource it, and am now almost ready to put it into the plugin repo, last few test cases to do, and a final smoke test. Im hoping to have it in the repository within the next few days.
Please be aware that this will be an alpha release.
The plugin will offer the follwing:
- Breadcrumb based navigation. Content and keyword controllers also output navigation structure objects to help building menus
- Friendly text rich URL's. (eg: /b/2009/04/this-is-a-blog-entry, /a/mycontent/content1/some-content-page.html)
- Very simple creation of content and tree like grouping structures, design aim is for non-developer to edit content
- Integration of JCaptcha and FckEditor for editing and comment control
- Integration of acegi security for content management
- Editing of both single and multipage content with keyword tagging that spans both blog and content pages
- Ability to enable and disable comments (and tagging information on content) on a per item basis
- Can create hidden groups (directories) of pages for use as landing pages
Limitations:
- Currently only saves images back to the file system. A database implementation may follow soon if there is interest
- Does not yet implement autosave on the blog and content management editors. (Fix in next release as this is annoying)
- No Ajax / javascript functions have been added, so every operation goes back to the server (Fix in next release)
- Only one level of security for the application, at the moment you cannot add extra permissions to groups for read / modify. Everyone can read, only logged in users can write. (More granular controls planned at group level)
- There is no versioning of old content, however this is a design goal and will be added soon. (Fix soon)
- Currently not internationalized, however it is my intention to make the plugin fully support many locales, including storing translations of documents in the database. However, this will be in a future release
Comments [2]
On 28-Apr-2009 03:54, sbglasius wrote:
This sounds cool. I have been in situations where I could use something like this. Looking forward to testing it.
/Søren (Denmark)
On 30-Apr-2009 16:22, Peter Bell wrote:
This is just what I was thinking of developing. Announce on the list or update the plugins page on the wiki when you release this as I'd love to play and maybe help contribute some features if you were interested . . .