-
Notifications
You must be signed in to change notification settings - Fork 133
User feedback and content update
nannanli edited this page Apr 19, 2019
·
11 revisions
User feedback is important to us. This section lists the user feedback on Zowe documentation and provides an update if any to each feedback. As a user, your feedback is not only heard. We value them and are making progress to address them to provide enhanced content experience.
This section documents the annonymous comments that are received in the following channels and which require content updates.
- NPS (Net Promoter Score) When a user stays on the Zowe doc site for sometime, an NPS board pops up asking the user how likely they are going to recommend Zowe Docs to other colleagues or friends. The user can also comment to provide more details.
- Zowe Documentation Survey The Zowe documentation survey is located on the navbar of the Zowe doc site which directs users to a Google Form where they will answer several questions.
User feedback in other channels including Slack are directly converted into GitHub issues for tracking.
- документация скудная. нет подробного описания переконфигурации компонентов (Google translate: The documentation is scant. No detailed description of component reconfiguration.)
- It would be highly helpful if someone can create an educational video on installing Zowe. Personal would like video for Installing Zowe CLI.
- There is very little information on how the apps in the ZOWE desktop work.
- Lack of information about problems faced during install. Have a list of errors/problems people have had when trying to install and provide possible solutions.
- Doc readiness checklist
- Doc planning
- Doc maintainers
- What is the Pull Request process and how to submit a PR?
- Build and Archive Legacy Documentation
- How to check broken links
- How to build PDF
- How to add a new file to the site
- How to build the site
- How to prepare appendix for a new release
- How to embed videos in Zowe docs
- How to write what's new/release notes
- How to report documentation progress and status?
- How to author in Markdown?
- How to author content or a new release? What process to follow?