The UX with editing the wiki, using WYSIWYG content editor [0] has been improved in recent releases. [1] I peeked into 15.2 (self-managed release coming on Friday, July 22) which brings rendering Mermaid, PlantUML, Kroki diagrams previews. [2]
Maybe the wiki can be worth to revisit in the future, there are more features underway, suggest diving into this epic [3]
> Issues have the same markdown support, we can use ctrl+v to insert screenshots, we can add tags to the issues, we can assign people to relevant issues, we can comment with new things to do/add, and we can use the search bar to find relevant content. All our "knowledge doc" is stored insides the issues of an empty project named "doc".
Great to see that you have found a workflow, and use issues to keep things documented and organized. Maybe a suggestion for creating an entry point into the dcc project: Use GitLab CI/CD to read the issues from the REST API, group by label, and render a Markdown README.md file which gets pushed to the repository automatically. That way the "index" is generated and provides greater visibility into the documentation issues.
I like API challenges, so I've hacked [4] a small script [5] using python-gitlab to better illustrate what I mean :-) Uses issues [6] with labels to generate an index.md [7] (can also be README.md for example).
Feel free to repurpose for your own needs, if that helps. The missing step is to automate it using GitLab CI/CD Schedules, but that's documented.
[0] https://docs.gitlab.com/ee/user/project/wiki/#content-editor
[1] https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-rel...
[2] https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86701
[3] https://gitlab.com/groups/gitlab-org/-/epics/5401
[4] https://gitlab.com/dnsmichi/api-playground/-/merge_requests/...
[5] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...
[6] https://gitlab.com/dnsmichi/api-playground/-/issues
[7] https://gitlab.com/dnsmichi/api-playground/-/blob/main/index...