Current version of the applications



Django-registration: v. 0.2  May 29th 2007
website: http://code.google.com/p/django-registration/

Sphene:  v 0.2  June 30th  2007
website: http://code.google.com/p/sct-project/

Satchmo: rev-407-2007-06-05
website: http://www.satchmoproject.com

Whee: none
website: http://code.google.com/p/whee/



The Goal
__________________

Today websites have a commom architecture that can be reused only changing the general layout.
Most of the time that you need to change something, it is something small and you
have a lot of work to create the infra-structure again and again. Django have really neat capabilities
like the sites and flatpages that make everything much easier for you, but now we have bigger needs like
stores, blogs, forums, wikis and a lot of other application and it's a lot of gather, look, find, test 
and so on. 
So, to make it easier to create a new website having in mind a CMS, I decided to create something
flexible and neat, but not that big piece of rock that there are around, on a language much more robust then
php. The applications are interchangeable, so you can "plug" in any project you want (most of them are
separated open-source projects), but, they all will be united by a CMS interface, like Django's Admin 
interface, but focusing on layout, fast publishing and site management instead of a all in one management
that Django have.
And, with such a good infra-estructure that Django have, like a wonderful User management, a neat Middleware
for intercommunication and Python wonderful mark-up, we have the flexibility to create one of the
best CMS available.
So, welcome to a next step of web development, where you have to worry about content, not coding - but 
you can change everything easy as 1-2-3.




The Project 
_____________________

The project is starting just now and it will be a long way to get it good enough. First some applications
will be developed or improved, like wiki, store, contact, mailing and forum, here or on project's
home-page. 
So, if you want to help until the CMS itself start, you can check the projects at the top of this document.
If you want to suggest, use the project tickets.



The idea behind
_____________________
 
What you mean about CMS for REAL content?

Think about CMS and you will think about something that have pre-defined general content that you make 
whatever you want with the same stone. Sometimes you call it books, sometimes you call it product, but
it's always the same thing. And if you want to integrate your CMS to another application it will be a
lot of "obscure" code.
So, a CMS must be able to get anything you want, even on a existing application, without much pain
and that's where Python comes.

The idea to get a model or any Python class on Kaleidoscope interface is, like admin and meta in Django,
add a subclass to your main class called CMS, like this:

class Model(models):
   #properties here

   class Admin:
      pass

   class Meta:
      pass

   class CMS:
      #information here



Neat, simple and easy as any Django implementation, uh?
And if you want to create a publishing interface?


class Model(models):
   #properties here

   def cms_publish_interface:
	return html_template

   class Admin:
      pass

   class Meta:
      pass

   class CMS:
      #information here


That's all, until we have something to show.