What are the most urgent additions to MODx ?

2 votes per voter ! (forum & ecommerce may be equally urgent)
It is always a good idea to have users stating clearly what are their expectations and priorities

Newsletter (hey I’m writing that when TP3.3 comes out)

Photo Gallery Integration (Galley 2/Coppermine)

Better module integration into the menu (adding a link to each module to the site menu)

Getting the user tracking out of the core. Easy enough to make a tracker module with a plugin or a snippet to keep whatever info you want.

But then I would also like to see web users and groups as a module too. Lots of small sites wouldn’t need the web login feature.

For that matter, why not make the manager user creation, roles, docgrops, etc (except for the main Admin user) a module as well? As far as I’m concerned, the more options I have to make a simple, basic website the happier I’ll be.

Newsletter plug/module (Go Mark you can do it)

all availible languages
options to install only that snippet if you want it and de install if not needed (remote downloading and installing? i think this is planned for TP4)

for me a ssl payament processor and new concept of shoping cart (or 99% of the web programs) like in the modules or snippets in the document a field who pass variables to the document content like you can do in plugins or snippets..(if could be whith more functions like checkbox or multicheckbox file upload and multiselect list) and whith the freature to show the code to administrator only for not lost the variable names asigned. the return of the sistem is a array of variables and you can use by mysql querry for search documents whith one variable or for create a master page to read this variables and show the content. now you only need to duplicate page and change the variables values for the new document.(i think you can do whith template variables but dont investigate now)
sorry for my bad english.

A thoroughly-documented walkthrough on how to build a module/plugin to integrate with other php apps (particularly a forum, or at least something with other user login/management needs)

A thoroughly-documented API.

Felini,

When’s the last time you checked out the documentation (http://modxcms.com/documentation)? There’s been a lot of work done, but there’s much more to come, particularly when things start getting much tighter post 3.3.

Hopefully we’ll have the SMF Module available soon so you can see how we handle a pretty serious module that integrates logins and synchs account changes. Requires 3.3, though, and still has some bugs to work through.

Quote from: Mark at Oct 18, 2005, 12:16 AM

Newsletter (hey I’m writing that when TP3.3 comes out)

Photo Gallery Integration (Galley 2/Coppermine)

Better module integration into the menu (adding a link to each module to the site menu)

Gallery 2 pretty well integrated will also be out post 3.3.

Quote from: Fellini at Oct 18, 2005, 10:14 AM

A thoroughly-documented walkthrough on how to build a module/plugin to integrate with other php apps (particularly a forum, or at least something with other user login/management needs)

A thoroughly-documented API.

I absolutely agree on this one. The current state of the documentation is good for the enduser who wants to know how he/she can make a site with
MODX.
For users who are are interested in the quality of the software and the structure of the software there is a lack of code documentation.
These type users often perform very important tasks as bug reporting and fixing.
Many eyes are needed to make stable software and if you guys are serious about modx, then it has to be a solid package. No serious user wants good looking software with lots of features when it does not perfrom wel or is not stable.

Opensource software needs good documentation for thechnical users and end users in order to be succesfull.

Good documentation attracts members, more members means more helping hands.

Fellini and alexw,

How are you two guys’ documentation skills? A small team can’t do it all as you’re well aware, and you both seem to have a grasp of exactly what you’re looking for. Who better to give it to you, well, than you?

You could perhaps have a conversation with some of the more technical folks on the dev team and document the findings. Many of the API calls are also already documented, but apparently you’re looking for more (and there is more to do)...

But also keep in mind that it’s somewhat of a moving target, particularly as we slow down the API features additions and start moving toward refarctoring for scalability and performance. (Things should actually become simpler...)

Thoughts?