As I had said earlier, I am going to finalize the
elevator pitch, it’s in my
september ToDo List.
I’ll post my ideas here later.
Right now, the first draft is aimed at designers, but I’d like to have the same kind of arguments for :
> content editors/content managers :
- QuickEdit
- the manager
- And how it can benefit the content editing experience
> coders
- define what modules/plugins/snippets are => the idea is focus on expandability
- insist on the advantages of the API and dbAPI => if someone can help me there... ? The idea would be to point out the faster dev time and anything advantage you can identify as distinguishing features of MODx
Please offer any input you might have on this, particularly the coder part
Thanks !
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
-
MODX Staff
- 12,272 Posts
@bindings for the coders ... with focus on @INHERIT in developing easy to maintain and customize column structures...
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
OK, nice leads... I hope I’ll be able to put this into words that will hit on with coders...
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id