The documentation is a very good start and we all should build on it. We should have some stuff for the power users also like a list of all the advanced setting with a one liner description of each setting as this is a very powerful feature to customize nopcommerce but most of the people are not aware of all the settings.
The documentation is a very good start and we all should build on it. We should have some stuff for the power users also like a list of all the advanced setting with a one liner description of each setting as this is a very powerful feature to customize nopcommerce but most of the people are not aware of all the settings.
I fully support this idea. Is there a way to get a list of those "unpublished" settings?
The documentation is a very good start and we all should build on it. We should have some stuff for the power users also like a list of all the advanced setting with a one liner description of each setting as this is a very powerful feature to customize nopcommerce but most of the people are not aware of all the settings.
It would be great we have better developer documentation. It misses a lot of topics. For example, "How to code a widget plugin", "How to add an item to the admin menu from a plugin", "How to customize [something]" (checkout), "How to override some service method in the plugin", "How to add extenal CSS or JS files in the plugin views", "How to add and implement a new message template", "How to add a new tab to admin area pages (to tabstrips) from a plugin", "A list of all available widgets", etc.
Any maybe improve some existing articles. For example, Exposing and Handling Events/ There could be some example, some real usage scenarios
It would be great we have better developer documentation. It misses a lot of topics. For example, "How to code a widget plugin", "How to add an item to the admin menu from a plugin", "How to customize [something]" (checkout), "How to override some service method in the plugin", "How to add extenal CSS or JS files in the plugin views", etc
I will publish some of them soon, we have them in our internal wiki, need to change few things before its ready to share.
One important issue that has to be taken into account is versions. The bulk of the contents of documentation is version dependent (example User and Developer guides). Fortunately Atlassian Confluence (whose own documentation also has versions) has features for managing versions. Maybe the documentation which is version dependent should be copied a few days before release of v3.50 and named for v3.40; and so in further releases.
Will the existing PDF User Guide of previous versions included within the Nop documentation? Recently I have still seen forum enquires for issues as far as v1.90.
One important issue that has to be taken into account is versions. The bulk of the contents of documentation is version dependent (example User and Developer guides). Fortunately Atlassian Confluence (whose own documentation also has versions) has features for managing versions. Maybe the documentation which is version dependent should be copied a few days before release of v3.50 and named for v3.40; and so in further releases. .
I agree with you Eduardo, some of content in the documentation is version dependent. Usually 90% to 95% of the things (or process) remains same in each version (unless there is a big change in any feature / functionality), so it shouldn't be difficult to maintain the documentation based on the version. But, at the same time, I think it will be lot of stuff to deal with every release in the documentation if it is maintained according to the versions.