I'll start with the applications that I've already evaluated and/or used:
Wikidpad
* Pros:\n fast switching between the edit and view modes;\n nice syntax (especially for pasting code snippets or just raw ASCII text, nice indenting visual clues);\n it is standalone application that don't require server;\n the wiki pages can be kept in flat text database;\n easy drag-and-drop of file attachments (especially for image files).\n* Cons:\n doesn't have history/version control of the pages and the state of the wiki database as a whole;\n doesn't have the concept of namespaces for the wiki pages;
MoinMoin wiki
* Pros:\n nice syntax;\n have standalone server (Python based) which makes it truly portable and standalone;\n keeps the pages in flat files;\n have a lots of nice plugins;\n* Cons:\nits a wiki == slow iterations of editing/taking notes, viewing, rince-repeat...\ndoesn't have version control integration
Trac
* Pros:\n All of the features of the MoinMoin wiki, except the flat file database;\n Version control integration: I can use the wiki changeset feature and the wiki pages as metadata of my personal codebase;\n* Cons:\n All of the general drawbacks of the wikis;\n Not truly portable;
todolist2 (by AbstractSpoon)
* Pros:\n fast, standalone todolist manager;\n the tasks have this really nice and important for me feature of having an rich edit box for taking notes associated with the task with flipping between the task and the notes with a single key;\n time tracking for the tasks;\n* Cons:\n doesn't have version control built-in (it has \"simple\" version control by just making an automatic backup copies of the project/data file with time stamp embedded in its name).\n it's hard to filter the tasks by urgency (in the GTD terms, it doesn't have the concept of the containers of tasks: Inbox, Maybe, Next action for each project, etc).\n it doesn't have cross-referencing/linking between the tasks in wiki-like fashion.
Thinking Rock
* Pros:\n implements GTD almost perfectly;\n it has notes for every action;\n portable;\n* Cons:\n (Maybe because of the Java GUI) doesn't have simple Undo when editing text notes;\n it's clunky when switching between the projects/actions tree and the editable notes editbox;\n doesn't have version control;
MonkeyGTD/TiddlyWiki
* Pros:\n truly standalone\n almost 100% wiki\n nice GTD implementation\n* Cons:\n it's little confusing when there is no easy or user-friendly way to see an overview of the current structure of the wiki pages\n I'm not sure if it scales well when there is a lots of pages/data/text/attachments.\n doesn't have source control integration;\n I'm not sure about version control/pages history...
So, to recap, I want an application that does the following:
* It has the speed and the ease of edit/preview iteration cycle of wikidpad.\n* It has the wiki pages and the associated attachments as they are (like wikidpad and MoinMoin).\n* It has version control for the wiki pages (like MoinMoin or Trac).\n* It has source control integration (like Trac).\n* It has the time tracking of the todolist2 and the task/project nesting like todolist2 and ThinkingRock.\n* It has the almost perfect GTD implementation of ThinkingRock or MonkeyGTD.
It's obvious that I haven't decided which one to use because for some reason my requirements are somehow orthogonal in the terms of the features that the aforementioned applications...not that the features are orthogonal or it is impossible or not practical...actually I think that maybe wikidpad is the closest to my ideal, which means that:\n* I decide to implement the features that I need (to add version control, GTD-life features/properties for the wiki pages themselves, source control integration), or\n* Continue to search and evaluate, or\n* Get some interesting and valuable opinions here
Thank you for your patience"},"title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Recommend a note taking wiki-like \"super\" application?"}},"_tags":["story","author_tripplez","story_1608933","ask_hn"],"author":"tripplez","children":[1609034,1609101,1609221,1609392,1611124],"created_at":"2010-08-16T19:40:51Z","created_at_i":1281987651,"num_comments":5,"objectID":"1608933","points":11,"story_id":1608933,"story_text":"Hello,
I'll start with the applications that I've already evaluated and/or used:
Wikidpad
* Pros:\n fast switching between the edit and view modes;\n nice syntax (especially for pasting code snippets or just raw ASCII text, nice indenting visual clues);\n it is standalone application that don't require server;\n the wiki pages can be kept in flat text database;\n easy drag-and-drop of file attachments (especially for image files).\n* Cons:\n doesn't have history/version control of the pages and the state of the wiki database as a whole;\n doesn't have the concept of namespaces for the wiki pages;
MoinMoin wiki
* Pros:\n nice syntax;\n have standalone server (Python based) which makes it truly portable and standalone;\n keeps the pages in flat files;\n have a lots of nice plugins;\n* Cons:\nits a wiki == slow iterations of editing/taking notes, viewing, rince-repeat...\ndoesn't have version control integration
Trac
* Pros:\n All of the features of the MoinMoin wiki, except the flat file database;\n Version control integration: I can use the wiki changeset feature and the wiki pages as metadata of my personal codebase;\n* Cons:\n All of the general drawbacks of the wikis;\n Not truly portable;
todolist2 (by AbstractSpoon)
* Pros:\n fast, standalone todolist manager;\n the tasks have this really nice and important for me feature of having an rich edit box for taking notes associated with the task with flipping between the task and the notes with a single key;\n time tracking for the tasks;\n* Cons:\n doesn't have version control built-in (it has \"simple\" version control by just making an automatic backup copies of the project/data file with time stamp embedded in its name).\n it's hard to filter the tasks by urgency (in the GTD terms, it doesn't have the concept of the containers of tasks: Inbox, Maybe, Next action for each project, etc).\n it doesn't have cross-referencing/linking between the tasks in wiki-like fashion.
Thinking Rock
* Pros:\n implements GTD almost perfectly;\n it has notes for every action;\n portable;\n* Cons:\n (Maybe because of the Java GUI) doesn't have simple Undo when editing text notes;\n it's clunky when switching between the projects/actions tree and the editable notes editbox;\n doesn't have version control;
MonkeyGTD/TiddlyWiki
* Pros:\n truly standalone\n almost 100% wiki\n nice GTD implementation\n* Cons:\n it's little confusing when there is no easy or user-friendly way to see an overview of the current structure of the wiki pages\n I'm not sure if it scales well when there is a lots of pages/data/text/attachments.\n doesn't have source control integration;\n I'm not sure about version control/pages history...
So, to recap, I want an application that does the following:
* It has the speed and the ease of edit/preview iteration cycle of wikidpad.\n* It has the wiki pages and the associated attachments as they are (like wikidpad and MoinMoin).\n* It has version control for the wiki pages (like MoinMoin or Trac).\n* It has source control integration (like Trac).\n* It has the time tracking of the todolist2 and the task/project nesting like todolist2 and ThinkingRock.\n* It has the almost perfect GTD implementation of ThinkingRock or MonkeyGTD.
It's obvious that I haven't decided which one to use because for some reason my requirements are somehow orthogonal in the terms of the features that the aforementioned applications...not that the features are orthogonal or it is impossible or not practical...actually I think that maybe wikidpad is the closest to my ideal, which means that:\n* I decide to implement the features that I need (to add version control, GTD-life features/properties for the wiki pages themselves, source control integration), or\n* Continue to search and evaluate, or\n* Get some interesting and valuable opinions here
Thank you for your patience","title":"Ask HN: Recommend a note taking wiki-like \"super\" application?","updated_at":"2024-09-19T17:07:34Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"vikramls"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"I prefer moinmoin - python-based, no need for a database and with per-page access control.
http://moinmoin.wikiwikiweb.de/"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Best Wiki Software?"}},"_tags":["comment","author_vikramls","story_49440"],"author":"vikramls","children":[49490,49679],"comment_text":"I prefer moinmoin - python-based, no need for a database and with per-page access control.
http://moinmoin.wikiwikiweb.de/","created_at":"2007-09-02T16:49:48Z","created_at_i":1188751788,"objectID":"49452","parent_id":49440,"story_id":49440,"story_title":"Best Wiki Software?","updated_at":"2024-09-19T16:21:35Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"SwellJoe"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"I've recently launched a wiki based on MediaWiki, which is the first deployment of MediaWiki I've done in about a decade. I have been really impressed. They've got technical debt, sure, but they're doing an excellent job paying it down, and moving forward without ever throwing away the whole project and starting over. I spent a lot of time evaluating wikis before relaunching this one (it was running on TWiki for years, on DokuWiki before that, and was a static site generated from DocBook XML or DocBook SGML before that), and was surprised to find MediaWiki was such a clear winner.
I probably shouldn't have been surprised, given the resources behind it and the size of it's userbase, but I still had notions that it would be like the MediaWiki of old: Slapped together rapidly, always barely ahead of the demands of WikiPedia and never having time to clean up and fix the warts.
I wrote a simple module for it, as well as an importer (using existing libraries to go from TWiki to MediaWiki markup, but we had some complexity coming over from such an old/large wiki), and found it really nice to work with. I don't like that it stores content in the database, rather than on the filesystem, but they provide such a nice import/export tool that I forgave them. And, performance is good; at least as good as the TWiki it replaced (which was also sufficiently fast), and much faster than some of the other similarly busy sites I maintain (this site gets about 60,000 visitors a month and a couple hundred thousand pageviews, and runs on a modest 4GB VM alongside several other sites).
In short, MediaWiki is a great example of an old project aging very gracefully. I'm happy to be working with it again. I'd become frustrated with wikis after several painful upgrades of TWiki that kept breaking things further and further until the site was barely functional Likewise, while DokuWiki and MoinMoin were great tools and I've used them to good effect a number of times, they haven't really seen the kind of advancements MediaWiki has had."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Modernizing MediaWiki with libraries"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://blog.wikimedia.org/2015/01/29/modernizing-mediawiki-with-libraries/"}},"_tags":["comment","author_SwellJoe","story_8970800"],"author":"SwellJoe","comment_text":"I've recently launched a wiki based on MediaWiki, which is the first deployment of MediaWiki I've done in about a decade. I have been really impressed. They've got technical debt, sure, but they're doing an excellent job paying it down, and moving forward without ever throwing away the whole project and starting over. I spent a lot of time evaluating wikis before relaunching this one (it was running on TWiki for years, on DokuWiki before that, and was a static site generated from DocBook XML or DocBook SGML before that), and was surprised to find MediaWiki was such a clear winner.
I probably shouldn't have been surprised, given the resources behind it and the size of it's userbase, but I still had notions that it would be like the MediaWiki of old: Slapped together rapidly, always barely ahead of the demands of WikiPedia and never having time to clean up and fix the warts.
I wrote a simple module for it, as well as an importer (using existing libraries to go from TWiki to MediaWiki markup, but we had some complexity coming over from such an old/large wiki), and found it really nice to work with. I don't like that it stores content in the database, rather than on the filesystem, but they provide such a nice import/export tool that I forgave them. And, performance is good; at least as good as the TWiki it replaced (which was also sufficiently fast), and much faster than some of the other similarly busy sites I maintain (this site gets about 60,000 visitors a month and a couple hundred thousand pageviews, and runs on a modest 4GB VM alongside several other sites).
In short, MediaWiki is a great example of an old project aging very gracefully. I'm happy to be working with it again. I'd become frustrated with wikis after several painful upgrades of TWiki that kept breaking things further and further until the site was barely functional Likewise, while DokuWiki and MoinMoin were great tools and I've used them to good effect a number of times, they haven't really seen the kind of advancements MediaWiki has had.","created_at":"2015-01-30T07:56:54Z","created_at_i":1422604614,"objectID":"8970981","parent_id":8970800,"points":null,"story_id":8970800,"story_title":"Modernizing MediaWiki with libraries","story_url":"https://blog.wikimedia.org/2015/01/29/modernizing-mediawiki-with-libraries/","updated_at":"2023-09-06T23:23:55Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"SwellJoe"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"The only one I've used is ZODB. The database was fine, I guess, but the Zope stack is huge and scary.
I can say that when it came time to move things to another non-Zope system (a pile made up of trac, Moin Moin, Virtualmin, and other bits and pieces), it was painful to the point of ridiculousness. I'm sure ZODB masters can write middleware for that sort of thing without pain (and if you're building your system that uses the ODB from scratch, you'll probably understand it well enough to do so). But I'll stick with standard cubbies in which to shove my things from now on (standard, to me, means flat files or an SQL database, as requirements dictate)."},"story_title":{"fullyHighlighted":false,"matchLevel":"partial","matchedWords":["datausa"],"value":"Ask YC: Object databases"},"story_url":{"matchLevel":"none","matchedWords":[],"value":""}},"_tags":["comment","author_SwellJoe","story_73972"],"author":"SwellJoe","comment_text":"The only one I've used is ZODB. The database was fine, I guess, but the Zope stack is huge and scary.
I can say that when it came time to move things to another non-Zope system (a pile made up of trac, Moin Moin, Virtualmin, and other bits and pieces), it was painful to the point of ridiculousness. I'm sure ZODB masters can write middleware for that sort of thing without pain (and if you're building your system that uses the ODB from scratch, you'll probably understand it well enough to do so). But I'll stick with standard cubbies in which to shove my things from now on (standard, to me, means flat files or an SQL database, as requirements dictate).","created_at":"2007-10-30T10:43:42Z","created_at_i":1193741022,"objectID":"74153","parent_id":73972,"story_id":73972,"story_title":"Ask YC: Object databases","story_url":"","updated_at":"2024-09-19T16:23:24Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"colas"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"I would advise using a wiki. Wikis fit well the programmers mental model as their main concept of editing \"source\" code that is compiled into a \"machine\" language (HTML). What wiki to use will depend on your favorite language or concepts. I use Foswiki http://foswiki.org (although I hate perl), because you can mix html/css/javastrict with the wiki syntax, and it has no database so I can hand edit easily the pages in emacs or use various shell hacks on them. But many nice wikis exist, for intance moinmoin is a nice one for python lovers.
I maintained my site with hand edited html, then I wrote a template engine for it, but for one year I have just ported everything on Foswiki (Foswiki is the active fork of TWiki), and have no regret. And if I want to add features, I can code plugins to it, use other people plugins."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Lightweight Programmer's CMS?"},"story_url":{"matchLevel":"none","matchedWords":[],"value":""}},"_tags":["comment","author_colas","story_700031"],"author":"colas","comment_text":"I would advise using a wiki. Wikis fit well the programmers mental model as their main concept of editing \"source\" code that is compiled into a \"machine\" language (HTML). What wiki to use will depend on your favorite language or concepts. I use Foswiki http://foswiki.org (although I hate perl), because you can mix html/css/javastrict with the wiki syntax, and it has no database so I can hand edit easily the pages in emacs or use various shell hacks on them. But many nice wikis exist, for intance moinmoin is a nice one for python lovers.
I maintained my site with hand edited html, then I wrote a template engine for it, but for one year I have just ported everything on Foswiki (Foswiki is the active fork of TWiki), and have no regret. And if I want to add features, I can code plugins to it, use other people plugins.","created_at":"2009-07-12T19:47:40Z","created_at_i":1247428060,"objectID":"700503","parent_id":700031,"story_id":700031,"story_title":"Ask HN: Lightweight Programmer's CMS?","story_url":"","updated_at":"2024-09-19T16:36:44Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"queensnake"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"Ugh, I use usemod, but am currently looking for a replacement. It's old, hasn't been touched since 2002, /doesn't/ have a plugin system, and its syntax has been superseded - its table support is primitive, for instance. Good points are, that it doesn't need a database, and, I dunno, it's useable, but the bar has been raised since then. I was looking at wikkawiki, but just now have found that what people have been saying about MoinMoin appeals to me. "},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Best Wiki Software?"}},"_tags":["comment","author_queensnake","story_49440"],"author":"queensnake","comment_text":"Ugh, I use usemod, but am currently looking for a replacement. It's old, hasn't been touched since 2002, /doesn't/ have a plugin system, and its syntax has been superseded - its table support is primitive, for instance. Good points are, that it doesn't need a database, and, I dunno, it's useable, but the bar has been raised since then. I was looking at wikkawiki, but just now have found that what people have been saying about MoinMoin appeals to me. ","created_at":"2007-09-03T19:46:44Z","created_at_i":1188848804,"objectID":"49754","parent_id":49480,"story_id":49440,"story_title":"Best Wiki Software?","updated_at":"2024-09-19T16:21:35Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"rstuart4133"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"My experience is different. I manage a wiki. It was a wonderful success in terms of getting people to contribute, however the wiki itself (moinmoin) has lousy authorisation and authentication tools, so I wrote my own. A few versions later changed to moinmoin broke those tools, but by that time most of time content has settled down so I just reverted locking down the system by making the user database read only (literally: "chmod -R a-w"). That worked well enough.
However every so often you would have to create a new account. To do that the chmod had to be undone, but only for a minute or two. In that minute or two typically 2 or 3 spam accounts where created, and maybe 20 wiki pages spammed or defaced.
In short: defending the site had no effect whatsoever for us. The bots were always probing, every few seconds, and it never stopped even years after the site was totally locked down.
PS: SPAM wise the bots were just an annoyance. But every page hit runs moinmoin's Python code, and it's not the fastest thing. We were running on low end VPS's that took a dim view of anybody using too much CPU. Our VM regularly got shut down because of those bloody bots."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"I accidentally built a nudity/porn platform"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://elazzabi.com/2020/08/11/the-day-i-accidentally-built-a-nudity-porn-platform/"}},"_tags":["comment","author_rstuart4133","story_24119024"],"author":"rstuart4133","children":[24128000,24129764],"comment_text":"My experience is different. I manage a wiki. It was a wonderful success in terms of getting people to contribute, however the wiki itself (moinmoin) has lousy authorisation and authentication tools, so I wrote my own. A few versions later changed to moinmoin broke those tools, but by that time most of time content has settled down so I just reverted locking down the system by making the user database read only (literally: "chmod -R a-w"). That worked well enough.
However every so often you would have to create a new account. To do that the chmod had to be undone, but only for a minute or two. In that minute or two typically 2 or 3 spam accounts where created, and maybe 20 wiki pages spammed or defaced.
In short: defending the site had no effect whatsoever for us. The bots were always probing, every few seconds, and it never stopped even years after the site was totally locked down.
PS: SPAM wise the bots were just an annoyance. But every page hit runs moinmoin's Python code, and it's not the fastest thing. We were running on low end VPS's that took a dim view of anybody using too much CPU. Our VM regularly got shut down because of those bloody bots.","created_at":"2020-08-11T23:08:58Z","created_at_i":1597187338,"objectID":"24127022","parent_id":24120103,"story_id":24119024,"story_title":"I accidentally built a nudity/porn platform","story_url":"https://elazzabi.com/2020/08/11/the-day-i-accidentally-built-a-nudity-porn-platform/","updated_at":"2024-09-20T06:44:53Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"ciprian_craciun"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"[OP: Bellow I'm describing what I'm searching for in a lightweight wiki engine, suitable for replacing MoinMoin.]
Now I know that there are many wiki engines, from dokuwiki and MediaWiki up to Bookstack and Wiki.js, however none of them fulfill the following requirements:
* first and foremost it has to use the file system to store the page content; one file per page (or per page history if it supports revisions); this excludes databases, including embedded ones like SQLite or the like; (basically I want to be able to cobbler together `find`, `grep` and `sed` to extract what I'm searching for if I want;)
* secondly it has to be lightweight enough so I can run it on my laptop; thus fiddling with NGinx and Apache is sub-optimal, as is having another 20-worker-process behemoth (I have enough Electron-ware already)... (for context, in my previous MoinMoin setup, I actually had two instances running, one on a public server and one on my laptop, and I've synchronized the files between them;)
* if possible it should come in a single binary (e.g. Go, Rust or C/C++), or at least be self contained (e.g. virtual environment); also NodeJS is out of the question just because I don't believe I'll be able to deploy it 5 years from now when the project is dead... (and no, I don't want to run a cluster of containers or even a single VM for my wiki... it's a wiki after all, not a web-scale search-engine with NLP built into it...)
* the UI shouldn't be more complex than it needs, thus a large text area for editing the page (without an WYSIWYG editor), lacking syntax highlighting, and not integrating with Jupyter Notebook are actually a plus; :)
* support for ACL's (for keeping sensitive pages private) would be a plus; (MoinMoin had the best ACL solution from all the wiki's I've seen so far;)
* (obviously, it must be open-source;)
So in the end why not just go with MoinMoin? Because I have the feeling the project is dead, and the stable version (1.9) seems to support only Python 2.7, which has just been EOL-ed and I believe it will slowly start to phase out from distributions repositories... Thus I wanted to see if there are alternatives..."},"story_title":{"fullyHighlighted":false,"matchLevel":"partial","matchedWords":["moinmoin"],"value":"Ask HN: Self-hosted lightweight wiki engine suggestions? (MoinMoin alternative)"}},"_tags":["comment","author_ciprian_craciun","story_23800862"],"author":"ciprian_craciun","children":[23801601,23801717,23802541,23804689],"comment_text":"[OP: Bellow I'm describing what I'm searching for in a lightweight wiki engine, suitable for replacing MoinMoin.]
Now I know that there are many wiki engines, from dokuwiki and MediaWiki up to Bookstack and Wiki.js, however none of them fulfill the following requirements:
* first and foremost it has to use the file system to store the page content; one file per page (or per page history if it supports revisions); this excludes databases, including embedded ones like SQLite or the like; (basically I want to be able to cobbler together `find`, `grep` and `sed` to extract what I'm searching for if I want;)
* secondly it has to be lightweight enough so I can run it on my laptop; thus fiddling with NGinx and Apache is sub-optimal, as is having another 20-worker-process behemoth (I have enough Electron-ware already)... (for context, in my previous MoinMoin setup, I actually had two instances running, one on a public server and one on my laptop, and I've synchronized the files between them;)
* if possible it should come in a single binary (e.g. Go, Rust or C/C++), or at least be self contained (e.g. virtual environment); also NodeJS is out of the question just because I don't believe I'll be able to deploy it 5 years from now when the project is dead... (and no, I don't want to run a cluster of containers or even a single VM for my wiki... it's a wiki after all, not a web-scale search-engine with NLP built into it...)
* the UI shouldn't be more complex than it needs, thus a large text area for editing the page (without an WYSIWYG editor), lacking syntax highlighting, and not integrating with Jupyter Notebook are actually a plus; :)
* support for ACL's (for keeping sensitive pages private) would be a plus; (MoinMoin had the best ACL solution from all the wiki's I've seen so far;)
* (obviously, it must be open-source;)
So in the end why not just go with MoinMoin? Because I have the feeling the project is dead, and the stable version (1.9) seems to support only Python 2.7, which has just been EOL-ed and I believe it will slowly start to phase out from distributions repositories... Thus I wanted to see if there are alternatives...","created_at":"2020-07-11T10:00:30Z","created_at_i":1594461630,"objectID":"23800870","parent_id":23800862,"story_id":23800862,"story_title":"Ask HN: Self-hosted lightweight wiki engine suggestions? (MoinMoin alternative)","updated_at":"2024-09-20T06:31:07Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"delano"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["moinmoin","datausa"],"value":"Yeah slowness is definitely \":(\"-worthy, but in my experience Confluence performs pretty well. It really depends how it's installed and how the database is setup also.
And the search is weak, I agree, but I haven't experienced any significant problems in scaling or Jira integration. It's also much more pleasant to deal with than SharePoint.
For technical-only teams, I highly recommend MoinMoin. It takes some hands on administration (maybe it's better now, I haven't used it for a couple of years) but it was worth it for the flexibility, plug-ins, and the fact that it stored pages in plain text files."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"How do you do in-company documentation (enterprise wiki)?"},"story_url":{"matchLevel":"none","matchedWords":[],"value":""}},"_tags":["comment","author_delano","story_219993"],"author":"delano","comment_text":"Yeah slowness is definitely \":(\"-worthy, but in my experience Confluence performs pretty well. It really depends how it's installed and how the database is setup also.
And the search is weak, I agree, but I haven't experienced any significant problems in scaling or Jira integration. It's also much more pleasant to deal with than SharePoint.
For technical-only teams, I highly recommend MoinMoin. It takes some hands on administration (maybe it's better now, I haven't used it for a couple of years) but it was worth it for the flexibility, plug-ins, and the fact that it stored pages in plain text files.","created_at":"2008-06-18T13:31:40Z","created_at_i":1213795900,"objectID":"220741","parent_id":220309,"points":null,"story_id":219993,"story_title":"How do you do in-company documentation (enterprise wiki)?","story_url":"","updated_at":"2023-09-06T19:17:04Z"}],"hitsPerPage":10,"nbHits":11,"nbPages":2,"page":0,"params":"query=MoinMoin+DataUSA&hitsPerPage=10&advancedSyntax=true&analyticsTags=backend","processingTimeMS":24,"processingTimingsMS":{"_request":{"roundTrip":21},"afterFetch":{"format":{"highlighting":1,"total":1},"merge":{"mergeLoop":{"prepareNextHit":4,"total":4},"total":6},"total":6},"fetch":{"query":13,"scanning":3,"total":17},"total":24},"query":"MoinMoin DataUSA","serverTimeMS":27}