ACME, a powerful content management framework written in Python
Be the first to post a text review of Agile Content Management Engine. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Hello -- and sorry for this long silence. The Roadmap had been dropped around a year ago when I decided to move towards semantic net as the model for Acme. The app was completely rewritten once again as Acme 0.8, and project status has been changed from 'beta' to 'alpha'. In December 2006 the Acme Community was established (http://ru_acme.livejournal.com). The conception of Acme has been seriously revised, and project status is now 'planning'. And -- no, we are not going to make another step back. :) Today kleptos_t has joined the project as co-maintainer. (Hurray!) Currently we are working on a prototype for semantic-driven model. The code will soon appear in SVN repository. By the way, we switched from Perl to Python. The whole conception is not clear yet, so this code is just something to play with and to understand whether this model is exactly what we need.
17 Jan 2006. The long-awaited Acme 0.7 "Spark" (unstable) is finished. I'm glad to report that we are being in time: this release, "Spark", was scheduled for a period from around December 2005 till early 2006. The sources are not published yet (see http://acme.sourceforge.net for details). Next aim is Acme 0.8 "Eyeglow". Again, see the homepage for detailed roadmap.
The development has been slowed down until February 2006 (as planned). STATUS: Currently there are working components for two of three major data classes (Category and Content) which provide generic support for some actions such as View, Edit, Rss. TODO: some type-specific action handlers for the two above-mentioned components; Admin and User components; better error handling. These are beta-blockers.
The API seems to be worked out; most planned abstract functions are written and tested. I'm now starting to merge the prototype into the trunk. The next step will be building two components (aka pluggable system modules) - Admin and Document. What I now want is to test the whole architecture in real conditions. This iteration's hardest expected task will be creating a module to cope with Nested Sets (for Admin component mostly). I have some drafts, but they are very raw. After preparing 2..4 components (roughly), I will work on the system core and related stuff. So, the work is being done.
If you are a developer, and are interested in working on Acme - why not join the team? No matter what your favourite web-programming language is. Really. Moreover, within some months we will need translators. I can support these languages shown on the Summary page, but of course at this time I would prefer focusing on programming. Also, adding other languages to the list would be an excellent work. We don't currently provide language files, but their drafts are long ready, so anyone interested can write me and get the files. Creating a good interactive web interface (as 'theme') would also be highly appreciated. Ideas about AJAX are welcome, too.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?