Intranet suggestions....
-
@stacksofplates said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
What about creating rules to allow users to see what you want them to see?
https://docs.requarks.io/wiki/admin-guide/manage-access-rights
-
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
What about creating rules to allow users to see what you want them to see?
https://docs.requarks.io/wiki/admin-guide/manage-access-rights
It still doesn't work that great. Its too much a pain to manage.
-
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
What about creating rules to allow users to see what you want them to see?
https://docs.requarks.io/wiki/admin-guide/manage-access-rights
I think what @stacksofplates was saying above was that you can use these rules to permit access, but the search still allows you to see some of the content. If you try to select it it won't take you to the page and allow you to see the full content, but the search may give you headlines or even a little data that shouldn't be visible without permissions. This is something that hopefully they will be able to iron out moving forward.
-
Is there any affiliation between this site and the MangoApps intranet-as-a-service? https://www.mangoapps.com all mangos look the same to me....
I need to redo a 15 year old HTML intranet. These all sound like great ideas, but what about for someone who has absolutely no clue about web hosting. I have been doing networking and desktop support here for 10+ years and never had a need to learn web hosting. I run my own blogs in WordPress, but I picked a theme and filled in the blanks. I do not think I could do any design, and am already overloaded. Just the thought of learning a whole new discipline to setup a local WP site, design, and support a company intranet is too much.
I really want a turnkey solution I can task a minion to upload content into then throw to the wolves and let them burn it down slowly with cat videos and fashion gossip.
-
@zombiewrangler said in Intranet suggestions....:
Is there any affiliation between this site and the MangoApps intranet-as-a-service? https://www.mangoapps.com all mangos look the same to me....
I'm gonna guess no by looking at their "About Us" page.
-
This WordPress theme + plugins looks nice, try the demo.
-
@bnrstnr Agreed, but caught my attention as I was software searching.... Reminded me to come here and read the posts.
-
@zombiewrangler said in Intranet suggestions....:
Is there any affiliation between this site and the MangoApps intranet-as-a-service? https://www.mangoapps.com all mangos look the same to me....
I need to redo a 15 year old HTML intranet. These all sound like great ideas, but what about for someone who has absolutely no clue about web hosting. I have been doing networking and desktop support here for 10+ years and never had a need to learn web hosting. I run my own blogs in WordPress, but I picked a theme and filled in the blanks. I do not think I could do any design, and am already overloaded. Just the thought of learning a whole new discipline to setup a local WP site, design, and support a company intranet is too much.
I really want a turnkey solution I can task a minion to upload content into then throw to the wolves and let them burn it down slowly with cat videos and fashion gossip.
Any of the wiki solutions mentioned above need no backend skills. You just spin up a vm and follow instructions to install. Once done you are always in the GUI.
-
What about atlassian.com/software/confluence ?
It works perfectly well as intranet. You can do a bunch of stuff. You can fully use the AD to login, to craft rules, who is able to read, write or even access the intranet (AD-groups). It's not free though, but it sadly works very well and can be installed on your host server.
You can even start pages for every department, so that public stuff from the HR for example can be read but all the IT-documentation stuff is hidden... -
@cherryman said in Intranet suggestions....:
What about atlassian.com/software/confluence ?
It works perfectly well as intranet. You can do a bunch of stuff. You can fully use the AD to login, to craft rules, who is able to read, write or even access the intranet (AD-groups). It's not free though, but it sadly works very well and can be installed on your host server.
You can even start pages for every department, so that public stuff from the HR for example can be read but all the IT-documentation stuff is hidden...It's pretty standard as a wiki goes. Expensive, though.
-
@scottalanmiller said in Intranet suggestions....:
@cherryman said in Intranet suggestions....:
What about atlassian.com/software/confluence ?
It works perfectly well as intranet. You can do a bunch of stuff. You can fully use the AD to login, to craft rules, who is able to read, write or even access the intranet (AD-groups). It's not free though, but it sadly works very well and can be installed on your host server.
You can even start pages for every department, so that public stuff from the HR for example can be read but all the IT-documentation stuff is hidden...It's pretty standard as a wiki goes. Expensive, though.
Thats true. At the end of the day you have to buy a licence to maintain the service.
Every company i worked on ended up throwing away their current solution for confluence. -
@cherryman If you are also using Jira and a few other Atlassian tools, then I'd pick Confluence too. But if it is your only tool from them, I don't think that it is a strong wiki entry on its own.
-
@cherryman said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@cherryman said in Intranet suggestions....:
What about atlassian.com/software/confluence ?
It works perfectly well as intranet. You can do a bunch of stuff. You can fully use the AD to login, to craft rules, who is able to read, write or even access the intranet (AD-groups). It's not free though, but it sadly works very well and can be installed on your host server.
You can even start pages for every department, so that public stuff from the HR for example can be read but all the IT-documentation stuff is hidden...It's pretty standard as a wiki goes. Expensive, though.
Thats true. At the end of the day you have to buy a licence to maintain the service.
Every company i worked on ended up throwing away their current solution for confluence.LOL, I've seen the opposite. Never met a company that was happy with Confluence and kept it. Seen loads try it, none keep it, including ones that use Jira.
-
@scottalanmiller said in Intranet suggestions....:
@cherryman If you are also using Jira and a few other Atlassian tools, then I'd pick Confluence too. But if it is your only tool from them, I don't think that it is a strong wiki entry on its own.
We are also using Jira to split up several ticket systems based on their usecase. Dev, Admins, Customer Service and so on.
I don't think that it is a strong wiki entry on its own.
Why not? I am not missing anything to be honest. You could argue about the price, but besides that, why do you thing it is not "strong". Just curiosity here: What are you missing in that tool?
-
@scottalanmiller I have to admit.... Jira is the worst piece of sh*t i've ever witnessed
Luckily i was able to switch the internal Customer Service ticket system to osTicket. -
@cherryman said in Intranet suggestions....:
Why not? I am not missing anything to be honest. You could argue about the price, but besides that, why do you thing it is not "strong". Just curiosity here: What are you missing in that tool?
Slow and a bit more effort to maintain than strong alternatives. Cost is a big factor, it's hard to overlook. Why pay rather a lot for something that free alternatives seem to do better. Same reason we don't use Jira. I've used it a lot in the past, and it just isn't normally as good as free options, and it isn't cheap. Neither is bad, but they don't tend to be good enough for people to want to use. Too complex for their own good.
What we've always found is that management dislikes them because of cost, development dislikes them because they aren't easy to use and waste dev time, and IT dislike them for being unnecessarily complex to support.
-
@cherryman said in Intranet suggestions....:
@scottalanmiller I have to admit.... Jira is the worst piece of sh*t i've ever witnessed
Luckily i was able to switch the internal Customer Service ticket system to osTicket.LOL, if you have full time Jira experts, it's not that bad. But it's never good. And the effort to make it "not that bad" is too high, haha.
-
Should be noted, Jira isn't a ticket system, so if you had tried to use it as that, it would definitely be painful. It's more of a KanBan PM tool.
-
@scottalanmiller said in Intranet suggestions....:
Should be noted, Jira isn't a ticket system, so if you had tried to use it as that, it would definitely be painful. It's more of a KanBan PM tool.
I know, basically my DEV department loves it, but we admins hate it because it makes no sense to use it as a ticket-system for basic stuff like "my PC does not work - did you tried turning it off and on again?"
LOL, if you have full time Jira experts, it's not that bad.
We don't have this kind of lovely people in the company i am working at haha
-
@cherryman said in Intranet suggestions....:
I know, basically my DEV department loves it, but we admins hate it because it makes no sense to use it as a ticket-system for basic stuff like "my PC does not work - did you tried turning it off and on again?"
LOL, if you have full time Jira experts, it's not that bad.
We don't have this kind of lovely people in the company i am working at haha
I rarely do but have in the past and it did a fair job. BUT it was never used as a ticket system, it was for project planning.
