I would like to say that I really appreciate the greater coverage of documentation for the new CMS. Having it accessible to the context is also very helpful – we eagerly await this feature in the white-label version also. Good documentation saves everyones time and makes partners more confident implementing and offering features.
The extent of features offered in the new CMS, along with the possible implementation scenarios, means that having exhaustive documentation is extremely difficult.
I would like to suggest that the partner community have the ability to contribute to the documentation in order to enable its expansion to be as comprehensive as possible. This may take the form of a wiki or similar. It may be worth having some moderation of posts, but that would still be an effective way to build out much richer content.
Partners could then provide very specific feature implementation scenario examples or just add more detail that we may have already been keeping duplicated personal notes on.
I would like to say that I really appreciate the greater coverage of documentation for the new CMS. Having it accessible to the context is also very helpful – we eagerly await this feature in the white-label version also. Good documentation saves everyones time and makes partners more confident implementing and offering features.
The extent of features offered in the new CMS, along with the possible implementation scenarios, means that having exhaustive documentation is extremely difficult.
I would like to suggest that the partner community have the ability to contribute to the documentation in order to enable its expansion to be as comprehensive as possible. This may take the form of a wiki or similar. It may be worth having some moderation of posts, but that would still be an effective way to build out much richer content.
Partners could then provide very specific feature implementation scenario examples or just add more detail that we may have already been keeping duplicated personal notes on.