Ideas for ITSP and MSP Internal and Customer Documentation
-
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
the formatting in Wikis is such a PITA to me that I would hate using them for documentation for clients. that's just me though.
Same formatting as NodeBB
Like that's any better
-
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
the formatting in Wikis is such a PITA to me that I would hate using them for documentation for clients. that's just me though.
Same formatting as NodeBB
Like that's any better
Markdown too hard for you?
-
@JaredBusch said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
the formatting in Wikis is such a PITA to me that I would hate using them for documentation for clients. that's just me though.
Same formatting as NodeBB
Like that's any better
Markdown too hard for you?
Don't you know it! I need WYSIWYG.
-
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
@JaredBusch said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@Dashrender said in Ideas for ITSP and MSP Internal and Customer Documentation:
the formatting in Wikis is such a PITA to me that I would hate using them for documentation for clients. that's just me though.
Same formatting as NodeBB
Like that's any better
Markdown too hard for you?
Don't you know it! I need WYSIWYG.
That's what Sharepoint tries to do and messes everything up.
-
I know this topic is quite old so my apologies. Whatever came of this though? I am looking for something at work to improve what we have, which is not really much. We use text files, word files, and spreadsheets for example and we need to do much better.
-
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
I know this topic is quite old so my apologies. Whatever came of this though? I am looking for something at work to improve what we have, which is not really much. We use text files, word files, and spreadsheets for example and we need to do much better.
Right now- NTG is using wiki.js
-
@gjacobse Ok thanks. Will start checking that out.
-
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
@gjacobse Ok thanks. Will start checking that out.
It I wasn’t on a phone, I’d search for the threads on it. But both @scottalanmiller and @JaredBusch have one here...
-
Bundy uses a mix of Bookstack and Nextcloud. Withthings lsowly being organized into Bookstack because WYSIWYG.
-
@JaredBusch Ok thanks. Will check out those too
-
Btw for anyone interested, I have used Boostnote a lot for code notes. It works great if you have a lot of that to document. I'll leave it up to you to decide to use that over something like Github or Gitlab though. So just mentioning it for anyone that might want something like that.
-
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
I know this topic is quite old so my apologies. Whatever came of this though? I am looking for something at work to improve what we have, which is not really much. We use text files, word files, and spreadsheets for example and we need to do much better.
Wow, this has been a while. I'll try my best to update. And I'm not saying where we are is great, but it is a massive improvement and we are pretty happy. We've looked at, and we keep looking at, BookStack, but I think that we've decided that it just isn't quite right for us. We do manage and use BookStack for a partner, though (and @valentina has been doing little else for weeks, she is doing full time BookStack management and is about to do the same for DokuWiki) and know it pretty well at this point.
Here is where we are today:
- wiki.js for our main documentation
- NextCloud + Collabora (LibreOffice) for secondary documentation
- Open Document formats
-
wiki.js is really close to a 2.0 release. I'd test now, but not implement until they update. They are moving to a completely different database engine.
-
@scottalanmiller Ok thanks. I was searching and this topic is what came up for me on google so that is only reason I posted to such an old topic.
We are currently not using any kind of official documentation except excel, text, and word. It may not happen but i want to keep pushing to get us on something better than that.
-
@scottalanmiller What db were they on and what are they moving to out of curiosity?
-
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller What db were they on and what are they moving to out of curiosity?
MongoDB and moving to PostgreSQL
-
@scottalanmiller Ok interesting.
-
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller Ok interesting.
It is ONLY for authentication and sessions, not content. So makes way more sense. Totally terrible use case for MongoDB.
-
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller Ok interesting.
It is ONLY for authentication and sessions, not content. So makes way more sense. Totally terrible use case for MongoDB.
So MongoDB will still be used for content?
-
@wrx7m said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller said in Ideas for ITSP and MSP Internal and Customer Documentation:
@jmoore said in Ideas for ITSP and MSP Internal and Customer Documentation:
@scottalanmiller Ok interesting.
It is ONLY for authentication and sessions, not content. So makes way more sense. Totally terrible use case for MongoDB.
So MongoDB will still be used for content?
No, it never was.
