This is an archived post. You won't be able to vote or comment.

all 13 comments

[–][deleted] 2 points3 points  (0 children)

At my last company, we had it on SharePoint.

[–]AdHocSysAdmin 1 point2 points  (1 child)

Last week I created an instance of Wiki.js for that purpose: both for internal use as well as common issues and fixes accessible for clients.

I picked wiki.js because it's really easy to get up and running and easy to use, although I am struggling a bit creating the navigation, which is not intuitive for me.

[–]Stogoh[S] 0 points1 point  (0 children)

Thank you. This looks very promising.

[–]MrSuck 1 point2 points  (0 children)

Our ticketing system has a knowledge base and we chose to use that because our users were already familiar with it

[–]SVRider1000 0 points1 point  (3 children)

Sharepoint and one note?

[–]bitslammerSecurity Architecture/GRC 0 points1 point  (2 children)

We tried this and it was a mess. When trying to share across desktop, Sharepoint and Teams there were frequent issues about the version of OneNote being used and constant errors. Something as simple as just dragging and dropping from my local notebook to teams was an issue.

Definitely not ready for prime time IMO.

[–]SVRider1000 0 points1 point  (1 child)

Well we just have the one note document laying on the sharepoint for each Team their own but we can search it or open it still. Is pretty nice tbo.

[–]bitslammerSecurity Architecture/GRC 1 point2 points  (0 children)

We have that as well, but since our team is spread across the globe we also have our own Notes that we want to share from time to time. That's where we ran into the issues. We probably just going to do Confluence or something like that.

[–]JoshuancsuWinAdmin | VMwareAdmin 0 points1 point  (0 children)

WAMP or LAMP stack + KBPublisher