Code "markdown" for OneNote?
-
What's worse is the Sharepoint wiki doesn't preserve code. It's a mess.
-
I just use our Gitlab server for documentation. It supports markdown and keeps it in version control.
-
Using Git probably does make a lot of sense.
-
I would absolutely use Sharepoint for documentation if it had better features.
OneNote is great for documentation, and the search functionality is amazing. It's just a shame that this feature is missing.
@stacksofplates I've never used GitLab. I'll have to check those guys out.
-
How about for internal documentation, such as an IT knowledgebase?
-
@NerdyDad said in Code "markdown" for OneNote?:
How about for internal documentation, such as an IT knowledgebase?
Let me expand this into keeping formatting for stuff such as PowerShell scripts.
-
@NerdyDad said in Code "markdown" for OneNote?:
@NerdyDad said in Code "markdown" for OneNote?:
How about for internal documentation, such as an IT knowledgebase?
Let me expand this into keeping formatting for stuff such as PowerShell scripts.
GIT still.
-
Could someone screen shot one of their IT KB articles on their GitLab? My experience with it was always the Dev side... nothing regarding IT wiki KBs or whatever you want to call them.
I'm interested to see what your GitLab article and area look like. Perhaps it's a better solution than the one I'm using now.
-
@Tim_G said in Code "markdown" for OneNote?:
Could someone screen shot one of their IT KB articles on their GitLab? My experience with it was always the Dev side... nothing regarding IT wiki KBs or whatever you want to call them.
I'm interested to see what your GitLab article and area look like. Perhaps it's a better solution than the one I'm using now.
It's ONLY the code that we put there, not articles. Well not here, anyway.
-
@scottalanmiller said in Code "markdown" for OneNote?:
@Tim_G said in Code "markdown" for OneNote?:
Could someone screen shot one of their IT KB articles on their GitLab? My experience with it was always the Dev side... nothing regarding IT wiki KBs or whatever you want to call them.
I'm interested to see what your GitLab article and area look like. Perhaps it's a better solution than the one I'm using now.
It's ONLY the code that we put there, not articles. Well not here, anyway.
Oh I see. I misunderstood.
-
@Tim_G said in Code "markdown" for OneNote?:
@scottalanmiller said in Code "markdown" for OneNote?:
@Tim_G said in Code "markdown" for OneNote?:
Could someone screen shot one of their IT KB articles on their GitLab? My experience with it was always the Dev side... nothing regarding IT wiki KBs or whatever you want to call them.
I'm interested to see what your GitLab article and area look like. Perhaps it's a better solution than the one I'm using now.
It's ONLY the code that we put there, not articles. Well not here, anyway.
Oh I see. I misunderstood.
Some GIT systems have a wiki for documentation, though. That's not uncommon.
-
@scottalanmiller You still do your main internal documentation in OneNote or SharePoint, or have you moved to something else?
-
@fuznutz04 said in Code "markdown" for OneNote?:
@scottalanmiller You still do your main internal documentation in OneNote or SharePoint, or have you moved to something else?
Still do. OneNote.
-
@scottalanmiller said in Code "markdown" for OneNote?:
@Tim_G said in Code "markdown" for OneNote?:
@scottalanmiller said in Code "markdown" for OneNote?:
@Tim_G said in Code "markdown" for OneNote?:
Could someone screen shot one of their IT KB articles on their GitLab? My experience with it was always the Dev side... nothing regarding IT wiki KBs or whatever you want to call them.
I'm interested to see what your GitLab article and area look like. Perhaps it's a better solution than the one I'm using now.
It's ONLY the code that we put there, not articles. Well not here, anyway.
Oh I see. I misunderstood.
Some GIT systems have a wiki for documentation, though. That's not uncommon.
Ya. Gitlab has a repo for the code and a whole other repo for documentation/wiki for that code by default.
