191–200 of 203 posts
Confluence + Jira is a common combination. It is good to have an alternative to one of these. Anyone has info or suggestion on what are good open source alternatives for Jira?
Can anyone with experience with multiple wiki platforms compare this with XWiki and/or MediaWiki. I may be asked to update $WORK's wiki, which is currently MoinMoin (IIRC), and am looking for anyone with more experience so I don't have to start testing from scratch. I've run MediaWiki before, but am not beholden to using it just because of past/current familiarity. Importing from MoinMoin would be nice, but not absol…
I'm currently helping set up a wiki for students of a STEM faculty, and we've settled on MoinMoin (v2, that is). We're broadly building on a previous MediaWiki setup, which we've found to be too "Wikipedia-oriented". I've looked at a few very extensible and featureful wikis (XWiki, Tiki Wiki, TWiki, Foswiki), but for our usecase, they seemed overwhelmingly big (I know, I'm not easy to please). They're all almost appl…
Just fyi, MediaWiki does have support for using a different page content mark up languages (Content models in mediawiki speak). In the default that's mostly only used for special purposes like CSS pages (See Special:ChangeContentModel), but the interfaces are relatively clean if you want to add your own.
The only issue I have with many Confluence alternatives is that they don't support multiple people editing the same document, at the same time, à la google docs. Does this? I can't tell from the landing page.
All real Confluence alternative (Confluence is a b2b software not a wiki tool) Notion, Guru, Slab, Slite ... are supporting that since their creation.
I can't exactly remember, why I did not chose Bookstack, but I was positively impressed with the demo. Nice to see its continuously evolving.
I myself chose wiki.js back then.
Glad to see any alternatives to confluence (or Atlassian in general). I've used Confluence for a good 4 years or so and for the life of me, I can not fathom why anyone would use this for storing documentation for code etc, as opposed to storing things direct in a repo. I can understand it's use somewhat for business folks, but even then, the way of organising things is abysmal, every solution (such as rich text editi…
In my old (and soon current again) shop we used confluence extensively, to get the best from both worlds we usually kept the documentation next to the code in markdown or asciidoc files and synchronized them to confluence in a CI/CD pipeline (confluence was read only for these sections) maybe I can open source these helpers when I'm back... a two way merge was also in the making :). we could sync whole file trees wit…
I once found a plug-in that did almost the same, allowed Confluence to read and render markdown files directly from (private) GitHub repos thus allowing me to get the best of both worlds!
- docs stays in the repo (thus is much more likely to actually get updated)
- docs get exposed in Confluence (thus is accessible for the business folks that does not do git)
- docs are easy to update (as you can use any editor: vi, emacs, IDE’s etc)
So conceptually the same as you’re solution ;-)
Unfortunately we did not implement the plug-in as we have too many eggs in the Jira basket (+1.000 users) which have the unfortunate side effect that the licensing price is derived from the +1000 users even though only the much lower number of devs would use it.
That is one repeated problem we face in the Atlassian stack (well a source of their income…)- even a seemingly cheap plugin (extension or whatever they’re called) ends up in the person suggesting how to ‘work smart/not hard’ having to find the funding typically a two digit thousands of € or year (thus I never bother with that anymore :(
I looked into Bookstack three years ago when searching a replacement with a better WYSIWYG editor for my DokuWiki instance so my wife could participate in the Wiki. I can't exactly remember, why I did not chose Bookstack, but I was positively impressed with the demo. Nice to see its continuously evolving. I myself chose wiki.js back then.
For me wiki.js had more capability for importing previously exported pages from OneNote and a more flexible document structure. In the end we went back to confluence though, as wiki.js lacked the capability to change the effective directory path of multiple pages (had to be done one at a time or via the API).
I really like both bookstack and wiki.js and they occupy a very similar niche. Do check them both out.
My ultimate wiki platform wishlist: comments module, markdown and attachment import/export, extremely fast tree hierarchy editor and renaming, and a good editor that enforces a fully standardized markup. Looks are nice too.
Whoa I can copy/paste images directly into the editor, sweet! One question though, if I deploy a containerized version via docker and upload images, where do the images reside (it seems like the php uploads folder? Just curious if I had to redeploy the image what volumes I might have to mount as back-upp
I used to use Dokuwiki as my personal notes app/knowledgebase pretty heavily. Switched to Bookstack two years ago and never looked back. It has everything you need in a Wiki, no third party plugins needed like Dokuwiki. The API is excellent, and I've used it to build some custom stuff. They recently added webhooks too. And Dan is pretty responsive on Discord if you need help.
Huh, so that's why the last update of Argon was 2 years ago :-) Thanks for making it! I consider it to be the best theme available for DokuWiki and my organization uses a forked version of it ( https://github.com/fablab-luenen/dokuwiki-krypton ).
Please add it to this listing as well https://www.dokuwiki.org/template
Earlier quoted context omitted.
In my old (and soon current again) shop we used confluence extensively, to get the best from both worlds we usually kept the documentation next to the code in markdown or asciidoc files and synchronized them to confluence in a CI/CD pipeline (confluence was read only for these sections) maybe I can open source these helpers when I'm back... a two way merge was also in the making :). we could sync whole file trees wit…
In my opinion this is the way to go, documentation close to the code but still indexed in a real knowledge management tool. That's one thing that we are building at Dokkument, but I would be really interested to know more about what you have done, especially how those files are then indexed on Confluence
Earlier quoted context omitted.
Huh, so that's why the last update of Argon was 2 years ago :-) Thanks for making it! I consider it to be the best theme available for DokuWiki and my organization uses a forked version of it ( https://github.com/fablab-luenen/dokuwiki-krypton ).
Thank you for making this. I added a link to your fork at the top of the repo's README. Please add it to this listing as well https://www.dokuwiki.org/template