@sottwell,
Hey Susan, that looks like an amazing tool! Have you tested it out?
@all
I awakened to a first thought about all this - and it's not intended to be pessimistic. Documentation (I have lead many doc projects) can always threaten to become a huge waste of time. For any documentation to be relevant, there needs to be some stability of change for the product. Otherwise, the docs and all the rich content are continually stale. So, #1 is that documentation becomes a valued part of the process and change impact is considered in a (forgive the buzzword), 360 degree fashion.
Community development is awesome and very powerful, however, it is also a culture that operates differently,with different norms, priorities and reasons for when things get changed and how. I have been with MODx for a long time but new to the community, so I will be respectful about what goes on here and not try to impose my views. Rather, I will share my experience.
I have seen systems that have become very costly (time and $) due to a lack of what I would call change management. We are talking about senior people in an organization calling for feature this and feature that and there would be no shepherding of the process.
If it is the case that the MODx UI is in constant flux, I would suggest some stability is required to make documentation worthwhile. It has become a mature product and having a UI build target would be great, rather than a continual sprinkling of "nice to haves." (not saying I know...just an if...then observation)
I am here to learn so willing to become more engaged in learning the change process and trajectory of Revo before I go waving my UX design wand around-we are all creative here and have many great ideas. I would consider being advisory and UX design + documentation participant and would be grateful to give back that way.
I'm going into the bowels of the MODx project stuff to educate myself.
Happy to keep this thread going.
T
MODX Staff
☆ A M B ☆