Forums / Cotonti / Core Labs / Ideas / Feature requests for 1.x branch

12>>>

Request big features here

Trustmaster
#1 2011-10-11 10:13

We have already started a discussion of 1.x to 2.0 roadmap, but I would like to see more feature requests for 1.x branch.

We have already added some features for developers on the list:

  • ORM integration
  • Structure-driven Views
  • RESTful API for web services and mobile development
  • Automated tests support

Here are user features we have in our minds so far:

  • Centralized extensions repository and online update.
  • Bridges to popular bulletin boards and image galleries.

 Please request major features which are very important to have for a competitive CMS/CMF.

  • Improved support for mobile devices.
May the Source be with you!
schulle4u
#2 2011-10-11 10:43

What about content converters/importers from other popular CMS to Cotonti? This would make Cotonti much more attractive for webmasters who wish to migrate their existing website from other systems and not just for those who want to build sites from scratch.

Steffen

signature://doesnt.exist
Trustmaster
#3 2011-10-11 12:55

That's a good idea! Though, each CMS will need a unique converter. A list of CMS which should be supported first of all is needed.

May the Source be with you!
Sergeich Online
#4 2011-10-11 12:59

drupal

wordpress

joomla

MODx 

TYPO3

DataLife Engine

schulle4u
#5 2011-10-11 14:09

PHP-Fusion. Just a personal wish, but perhaps it'll make it in the list of supported systems. :)

signature://doesnt.exist
esclkm
#6 2011-10-12 16:23

I need cotonti like Lego Blocks)

For ajax)

Like - I delete post -And It will be deleted on page - and in the botton of posts - will appeared next post

littledev.ru - мой маленький зарождающийся блог о котонти.
снижение стоимости программирования и снижение стоимости производства разные вещи. Первое можно скорее сравнить с раздачей работникам дешевых инструментов, чем со снижением зарплаты
Trustmaster
#7 2011-10-13 08:34
#30974 esclkm:

I need cotonti like Lego Blocks)

For ajax)

Like - I delete post -And It will be deleted on page - and in the botton of posts - will appeared next post

No, "everything is an AJAX block" is impossible to implement with Cotonti, at least in 1.x.

May the Source be with you!
GHengeveld
#8 2011-10-14 13:40

To be honest, I agree with esclkm. It's certainly a goal for 2.0.

Trustmaster
#9 2011-10-15 07:41

OK, for 2.0 that's acceptable.

May the Source be with you!
esclkm
#10 2011-10-15 11:29

make cotemplate interface class: for give: chance replace from tpl html parser to xml/json parsers

littledev.ru - мой маленький зарождающийся блог о котонти.
снижение стоимости программирования и снижение стоимости производства разные вещи. Первое можно скорее сравнить с раздачей работникам дешевых инструментов, чем со снижением зарплаты
Dyllon
#11 2011-10-17 03:54

I have a few suggestions; although they are not directly related to the official cotonti package more-so to cotonti.com.

  • Seperate extensions/themes for each branch of cotonti (i.e. have a section for Siena extensions, and a section for Geona extensions). It can be quite confusing since there is no direct way to tell until you download the extension/theme.
  • Adding a "store" would be ideal for extension developers/theme makers to sell some premium content; although, perhaps a list of willing coders would suffice somewhere? Or something to identify this user sells extensions/themes.

The first one has been bothering me recently. It just seems unnecessary to have two branches of extensions mixed in with eachother; when they aren't compatible with each other.

We are what we repeatedly do. Excellence then, is not an act, but a habit.
Twiebie
#12 2011-10-17 07:44
#31014 Dyllon:

I have a few suggestions; although they are not directly related to the official cotonti package more-so to cotonti.com.

  • Seperate extensions/themes for each branch of cotonti (i.e. have a section for Siena extensions, and a section for Geona extensions). It can be quite confusing since there is no direct way to tell until you download the extension/theme.

Very true, a new Cotonti user will have no idea about what is compatible and what is not.

GHengeveld
#13 2011-10-17 19:29

I've added a 'compatible with' field for extensions. We'll first have to update all the pages to have this information before I can add an actual filter for it.

Today I've fixed the extension type filter on the extensions page. It's not really useful yet because there aren't any modules in there. I'll add my Find module soon so there will at least be one in there. Hopefully many will follow. It's possible we will put the modules that come with Cotonti by default in there too.

tensh
#14 2012-03-29 08:25

I didn't dig extensively into Siena's features, but... is there a frontend for creating categories? (so that e.g. users with proper rights can add/delete categories)

Now in Genoa it's partially solved by a plugin "Blogs" (and it's buggy), but I think it's a neccessity for a CMS/CMF like that to enable creation of categories from frontend.

Every container category would have to have some additional settings, like e.g.
- optional limit of "one subcategory per user",
- optional "user gets administrative rights per category created",

... and a feature that detects duplicate category names would be needed.

Trustmaster
#15 2012-03-29 16:20

You're not alone with this request, see #819.

May the Source be with you!

12>>>