Roadmap after 2.0.0
November 12, 2009
Now that 2.0 has landed we would like to talk about the future.
We already have a frontedit branch with the frontend editing functionality and some other new features. Also a new Dashboard for the standard django admin is in the works. These features will be in 2.1.
If you have your own pony you would like to see it in 2.1:
- 1. Create a ticket on github.
-
- 2. Vote in the issue tracker at: http://github.com/digi604/django-cms-2.0/issues
- Or fork and start coding :)
A target date for 2.1.0 will be end of year or January. In mid December we will have a feature freeze.
The road to 2.2
For 2.2 we will see a major refactoring coming along that already started in the newadmin branch with the help of fivethreeo.
- - The current monolithic admin classes will be split.
- - the plugins will be working in other apps
- - the tree will be working in other apps
- - the menu will get its own app.
Related tags: roadmap
Comments
03:59
is there any way to create passthrough blocks, content of which will be inherited by child pages?
04:38
Would there be a way to add view / edit permissions by user groups? Currently you can hide a page from the menu based on if someone is logged in. That is great however can you take it one step further? and show content based on the group a user belongs to that is logged in? For example show "employee" links if an employee is logged in or show "Gold Customer" links if a gold customer is logged in etc...
17:17
Could you ask your questions directly here http://groups.google.com/group/django-cms?hl=en or http://github.com/digi604/django-cms-2.0/issues. They will be answered way faster that way :-)
19:36
I just read the install from documentation - to tell the truth, I did not understand anything. I am not a total idiot but, obiously, also not a python programmer, just an admin who wants to check a good python cms to get away from php horrors - but what I see here is far, far away from beeing usable for the "mainstream web guys" - php will rule with cms that work right out of the box for a long time. You guys should rethink what was meant with "software HAS TO be easy!". THANKS!
10:52
gongo: I think you are confusing installing PHP based applications and actually programming in PHP.
23:32
no 2.1.0 yet?
BTW is it OK that 'Kommentar absenden' isn't translated on this page?
(and error messages also)
07:13
Looking forward to the future of django cms. I just stumbled upon the page, and have nothing but high hopes! I think it would be great idea to
03:49
I just installed django for the very first time today. Trying to install django-cms using the installation instructions and whatever comments I've gleaned from this group. However, it seems that the instructions are not written for noobs like me.
I just need a little bit of hand-holding to complete the installation. The installation is on a shared hosting platform. Here's what I have done so far:
1. Django has been installed in ~/.local/lib/python (using python 2.4.3)
2. Flup has also been installed in same place
3. Created my app (site) directory - ~/.local/lib/python/eck
4. downloaded and extracted django-cms into ~/.local/lib/python/eck
5. Copied the cms, mptt, and publisher folders into ~/.local/lib/python/eck
That's where I'm stuck. Not sure what to do from here. Should I copy the contents of the example folder into ~/.local/lib/python/eck and customize the existing settings.py file? Or do I have to touch a settings.py and follow the rest of the instructions?
TIA
20:28
@finid: you're so right. I am not a Django noob, neither am I new to python or programming, yet the directions given in the optimistically called "Documentation" section of this site are not exactly helpful. One get's to configure a lot (coming from Zope and .zcml it was a delight actually writing a python config) but a real ToDo like "Get your own page started in 20 steps" would be really great. After all, just saying "copy this'n'that to a place where you can find it" is not exact;) Maybe one or two examples would help to illustrate.
on a side note: advertising workflowm, MAM, versioning and multisite-capability is great. All features i might want to use... but where's the docs for it? having no docs at all is worse than having Zope docs ;)
no offense guys, i really like what you are putting up here and wish to use it as a replacement for Plone HOPEFULLY. but you have to work on the documentation.
keep up the good work!
kingair_six