Good stuff as usual Shane.
You mention:
IMO the documentation should not cater to ’content editors’ or ’designers’ and only to general all purpose users. Leave the user specific stuff to how-to guides and keep the documentation focused on the application and not based on the user.
I am not sure I agree here. One of the things I notice with some other CMS documentation enterprises (like Wordpress) is that they do take the content creator in mind. Some documentation can list a zillion technical features with every module or snippet parameter possible. But for someone who is contemplating or starting out with MODx is that really a great way of presenting the material?
I like roadmaps: showcase great site structure and explain the MODx building blocks and pathways needed to achieve similar results. Documentation can be just that: pure documentation. But great documentation presented in imaginative ways can spark imagination and get people excited with the possibilities.
One of the most successful series of graphics how to books is the "Wow" series, like Photoshop Wow etc. You thumb though the pages and you go "wow, do you do that?" and the books tells you how to get there...
Max
☆ A M B ☆
MODX Staff
☆ A M B ☆
MODX Staff
