Process feedback from Group Level Wiki Research
Problem to solve
ux-research#340 (comment 252931340)
Below is the research from issue:This is the first iteration of the affinity map for Wiki: https://app.mural.co/t/gitlab2474/m/gitlab2474/1568158067615/4dc5906f46d3f96c7538e705c65068352f06a657. It includes feedback and comments from prior UX research and top 10 feature proposals in the GitLab issue tracker. This is an evolving board that we should add more feedback to as we continue to learn!
Summary
There are a variety of areas in which we can improve the Wiki feature - from navigation, editing, collaboration, permissions and more. The key thing for us to keep in mind is that many companies are working with the Wiki from both the developer perspective and a non-technical perspective. This means that a common pain point for teams is having a simple, efficient way to have less-technical users interact with the Wiki and access the information they need.
Common Use Cases for Wiki
- Using Wiki for "gotchas" - things that not everybody knows, general procedures and knowledge
- Internal documentation for processes such as migrations to new tools
- Documenting information relevant across projects (e.g. how to manage tickets, how to run and install projects, style guidelines, etc.)
Top 5 Feature Requests:
- Group-level Wiki, 576 upvotes: #13195 (closed)
- Allow org-mode in Wiki, 177 upvotes: #19688 (closed)
- Export Markdown pages to PDF, 158 upvotes: #13932 (closed)
- Update wiki page (.wiki.git) from CI, 133 upvotes: #16261
- Diff functionality in Wiki, 132 upvotes: #15242 (closed)