Wiki.js vs. SharePoint: Which is Better for a New Documentation Platform?

0
14
Asked By TechieNinja42 On

I'm a Junior SysAdmin and I've been tasked with creating a documentation wiki for my company. The requirements I have to consider are: a zero budget (so open-source is necessary), support for the Italian language, and three access levels (public, internal, and third-party). Additionally, we need to implement expiring permissions for some users. After researching various options like Wiki.js, SharePoint, and others, I'm leaning towards Wiki.js but my boss wants to know why it's a better choice than SharePoint. I've noted some key points: Wiki.js offers a more intuitive user experience, is built specifically for documentation, and is easier to manage. However, I have concerns about security and user management with Wiki.js. I'm looking for feedback on whether I'm missing any important security considerations or if managing user access will be a hassle for a medium-sized team. Have others opted for Wiki.js over SharePoint, and did you have any regrets?

5 Answers

Answered By LinuxWarriorX On

I can't say much about SharePoint since my background is mostly Linux-things, but I've had nothing but positive experiences with Wiki.js. The setup might take some thought regarding how you want your sidebar and links organized, but once you get it going, it’s super easy to navigate. Just keep in mind that while you could manage permissions from your identity provider, you’re going to want to check if expiring permissions can really work in Wiki.js as you need.

Answered By SkepticSteve42 On

I’ve heard mixed things about Wiki.js too; people have suggested it might be on its way out. Before you commit, you might want to check out options like Outline or Bookstack; they’re modern, packed with features, and worth your consideration. Document your requirements clearly before taking your pick, especially if you need Italian language support.

Answered By JustAnotherUser223 On

Honestly, SharePoint can be a nightmare for documentation. I haven’t used Wiki.js, but I know a lot of folks recommend solutions like Confluence that handle basic documentation needs much better. Just a heads up, though: if compliance is a big deal, a wiki alone might not cut it. You'll probably want a Document Management System (DMS) alongside your chosen platform.

Answered By NotBiasedAtAll On

Let's be real, your "real answer" against SharePoint seems based more on personal bias than solid reasoning. If your company has already bought into Microsoft products like Office 365, it might not be the best idea to ignore that. SharePoint likely integrates way better with your existing setup. You should consider offering a more objective evaluation of both platforms. Plus, while people talk about moving away from SharePoint, it hardly ever happens unless you’re ditching the whole Microsoft ecosystem.

Answered By OpenSourceFan99 On

From my experience, SharePoint is definitely not the best route for documentation. It's cumbersome to manage, and most people find the interface confusing. I'd bet you could set up Wiki.js in days instead of the month it would take to get SharePoint going. Plus, you'll avoid the need for extensive training but really think carefully about how you want to structure everything. If you hate SharePoint, why not just stick with Wiki.js? You can always switch later if it doesn't work out, but make sure to get some testing in first.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.