Hey sytse. This is the issue number [0]. There's a few people at the company I'm working at who have been pushing really hard to move away from GitLab to GitHub. One of their main issues, from what I can tell, stem from this issue and getting some integrated support for monorepos. I'm very glad you're working on the features monorepos require.
Aside from monorepos there is one other small issue I have with GitLab. GitLab is perfectly well situated to completely take over the software development planning, warehousing, deployment, and testing. Documentation is really the last front. If GitLab wikis were as powerful as Confluence I would be very happy because I'd never need to use that terrible bloated site ever again. I've been pushing for us to switch to GitLab wikis for a while but 2 coworkers keep saying that "it is not good for long-lived out-of-project documentation, it's not as searchable, you can't drag and drop for graphs, it's not as integrate, and it doesn't have as many features as Confluence".
I hope one day GitLab can be my one-stop-shop for everything.
Thank you very much for making such an amazing product.
Thanks for linking the issue. I'll discuss it with our product leaders.
Regarding the documentation we see many people switching to static websites generated with GitLab pages. This allows you to separate the change from the approval. Is this an option for you?
Personally I think that works and gives you all of the "edit-locally" benefits (Accessibility, hotkeys, versions, distributed/backed up etc). What that doesn't give you is a few other important features.
My coworkers are concerned with the following:
- Highlight and right click docs -> new ticket
- Drag and drop flow chart creation
- Non-developers can document and plan
- Full text search
- "Name spaced"/grouped documentation
- Third party integration
I agree that most of those are not in the wiki nor in GitLab pages.
For non developers you can make it easier to edit by linking the bottom of each page to the reposity. See our website or docs pages for an example of that.
Aside from monorepos there is one other small issue I have with GitLab. GitLab is perfectly well situated to completely take over the software development planning, warehousing, deployment, and testing. Documentation is really the last front. If GitLab wikis were as powerful as Confluence I would be very happy because I'd never need to use that terrible bloated site ever again. I've been pushing for us to switch to GitLab wikis for a while but 2 coworkers keep saying that "it is not good for long-lived out-of-project documentation, it's not as searchable, you can't drag and drop for graphs, it's not as integrate, and it doesn't have as many features as Confluence".
I hope one day GitLab can be my one-stop-shop for everything.
Thank you very much for making such an amazing product.
[0] - https://gitlab.com/gitlab-org/gitlab-ce/issues/18157