blocks|key|2795800|text|你真的无法打败汇合点，尤其是10美元(10美元或更少的用户)。我们在我的工作中使用它，它真的很棒。不过，这个组织需要一点时间来适应。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.atlassian.com/software/confluence/^0|7|3|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

You really can't beat <a href="http://www.atlassian.com/software/confluence/">Confluence</a>, especially for $10 (for 10 or fewer users). We use it at my job and it is really fantastic. The organization takes a little getting used to, though.

blocks|key|964613|text|我发现MediaWiki+wiki非常灵活和有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|964614|作为一种奖励，这对于使用过维基百科的人来说是非常熟悉的。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mediawiki.org/^0|3|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

I've found the <a href="http://www.mediawiki.org/">MediaWiki</a> wiki to be very flexible and useful.

As a bonus, it's very familiar to anyone who's used Wikipedia.

blocks|key|2796131|text|免责声明:我为雾溪工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2796132|FogBugz的wiki很棒，因为它与应用程序的其他部分集成了，但是编辑器是错误的。好消息是我们正在进行一次重大的改造。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://fogbugz.com/^0|0|0|7|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

Disclaimer: I work for Fog Creek

The <a href="http://fogbugz.com" rel="nofollow">FogBugz</a> wiki is great because it's integrated with the rest of the app, but the editor is buggy. The good news is we're doing a major revamp.

blocks|key|2796214|text|我有一个不推荐的Wiki+:一个可用于Sharepoint内部网的网站。完全是一种痛苦的利用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I have one non-recommended Wiki : the one available for Sharepoint intranet sites. Utterly a pain to use.

blocks|key|2796100|text|我建议ScrewTurn为wiki。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2796101|您还可以查看AxoSoft+OnTime，它是用于bug跟踪、scrum/敏捷项目管理、dev+wiki、帮助台等的非常好的软件。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.screwturn.eu/|1|http://www.axosoft.com/ontime^0|3|9|0|0|6|E|1^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

I suggest <a href="http://www.screwturn.eu/" rel="nofollow">ScrewTurn</a> for wiki.

You can also take a look at <a href="http://www.axosoft.com/ontime" rel="nofollow">AxoSoft OnTime</a> which is very good software for bug tracking, scrum/agile project managment, dev wiki, help desk and more.

blocks|key|964666|text|我们使用DokuWiki|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|964667|这里是DokuWiki、MediaWiki、TWiki和TracWiki的比较图表。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dokuwiki.org/dokuwiki|1|http://www.wikimatrix.org/compare/DokuWiki%2BMediaWiki%2BTWiki%2BTracWiki^0|4|8|0|0|0|2|1^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

We use <a href="http://www.dokuwiki.org/dokuwiki" rel="nofollow">DokuWiki</a>

<a href="http://www.wikimatrix.org/compare/DokuWiki+MediaWiki+TWiki+TracWiki" rel="nofollow">Here</a> is a comparison chart between DokuWiki, MediaWiki, TWiki and TracWiki

blocks|key|965225|text|如果有人在考虑TWiki+(我在2000-2008年期间是一个开发人员的Wiki+)，请记住查看叉-+http://foswiki.org。当TWiki商标持有者把这个项目重新发明为“商业开放源码”时，我们觉得我们不得不分叉，降低了我们决定如何志愿工作的能力。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/TWiki|1|http://foswiki.org/^0|7|5|0|1F|I|1^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]|$A|Q|B|R|1|S]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]|K|$5|F|G|H|C|$I|L]]]]

In case anyone's considering <a href="http://en.wikipedia.org/wiki/TWiki" rel="nofollow">TWiki</a> (the Wiki I was a developer on from 2000-2008), please remember to check out the fork - <a href="http://foswiki.org" rel="nofollow">http://foswiki.org</a>. We feel we were forced to fork when the TWiki trademark holder re-invented the project as 'commercial open source' and reduced our ability to determine how we would volunteer our time.

blocks|key|964822|text|我建立了一个内联网的网站，以传播研究和技术知识，但肯定不是技术熟练的人群。我尝试了几种解决方案，而PMWiki是最好的解决方案。易于管理，大量的“插件”，皮肤和扩展从使用它的人，较少的技术人员很容易使用，并有一个庞大的基础，它不会被放弃很快。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|964823|它是在文件服务器上设置一个替代随机电子邮件或word文档的选项。一个“知识管理系统”。我发现它比TWiki更容易使用。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.pmwiki.org/^0|1D|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

I setup an intranet site for disseminating research from and to technically savvy, but certainly not technically proficient crowd. I tried several solutions, and <a href="http://www.pmwiki.org/" rel="nofollow">PMWiki</a> is the best. Easy to administer, LOTS of "plugins," skins and extensions from the people using it, easy for less-technical folks to use and with a large base, it won't be abandoned anytime soon.

It was to setup an alternative to random emails or word docs on a file server. A "knowledge Management System." I found it much easier to use than TWiki.

blocks|key|2796163|text|多年来，我们尝试了大多数wiki包，但没有取得什么成功。要获得足够的牵引力，让开发团队和项目团队真正使用它是很困难的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2796164|在我们把电子邮件和日历转换到Google企业之后，我们就淘金了，因为它还附带了“网站”。事实证明，谷歌网站可以作为一个非常灵活和易于使用的wiki工具。内置的公共/私有/共享的东西，所以有些网站可以公开面对，而其他的是内部(通过谷歌应用程序ID)。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Google_Sites^0|0|1D|4|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

We tried most wiki packages over the years with little success. It was just tough getting enough traction to get the development and project teams to actually use one.

We struck gold after we had converted to Google Apps enterprise for email and calendar as it also comes with "Sites". It turns out <a href="http://en.wikipedia.org/wiki/Google_Sites" rel="nofollow">Google Sites</a> can work as a very flexible and easy to use wiki tool. Built in public/private/sharing stuff too so some sites can be public facing while others are internal (by Google Apps ID) only.

blocks|key|964958|text|我们在我经营的公司里使用大会。它们提供无限制的代码托管(Git/SVN)、票务、wiki、scrum和其他有用的工具，而且成本不高。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.assembla.com/^0|C|2|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

We're using <a href="http://www.assembla.com" rel="nofollow">Assembla</a> in the company I run. They provide unlimited code hosting (Git/SVN), ticketing, wiki, scrum and other useful tools, and doesn't cost much.

blocks|key|964634|text|我喜欢代码伪造类的应用程序，比如Trac或Redmine，如果您有地方托管它的话。或者谷歌代码/+SourceForge免费托管选项，如果你不介意做你的项目开源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I like the CODE FORGE kind of applications, like Trac or Redmine, if you have some place to host it. Or Google Code / SourceForge for free hosted options if you don't mind doing your projects open source.

blocks|key|2795896|text|PBWorks为项目协作提供了一系列特性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://pbworks.com/^0|0|7|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

<a href="http://pbworks.com/" rel="nofollow">PBWorks</a> provides a bunch of features for collaborating on a project.

blocks|key|964745|text|我喜欢37信号的巴塞坎普软件。您将获得一个非常好的、廉价的托管解决方案，并具有许多有用的特性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://basecamphq.com/signup^0|8|4|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I like 37signals's <a href="http://basecamphq.com/signup" rel="nofollow">Basecamp</a> software. You get a great, inexpensive hosted solution with a lot of useful features.

blocks|key|964835|text|我一直在和我的团队一起使用红地雷。它是免费的，并且有一个足够的wiki。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I have been using redmine with my team. It is free and has a wiki that is more than adequate.

blocks|key|2796182|text|Github和基特立德都包含wiki。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.github.com/madrobby/scriptaculous/|1|http://gitorious.org/statusnet/pages/Home^0|0|6|0|7|4|1^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]|$A|Q|B|R|1|S]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]|K|$5|F|G|H|C|$I|L]]]]

Both <a href="http://wiki.github.com/madrobby/scriptaculous/" rel="nofollow">Github</a> and <a href="http://gitorious.org/statusnet/pages/Home" rel="nofollow">Gitorious</a> include wikis.

blocks|key|2796194|text|几个月前，我在开发项目中也遇到了同样的困境。我们使用心触是因为它是免费的(Mindtouch+Core)，它有很多伟大的扩展，它的设计是现代和灵活的，文件附件和链接功能是全面的，它可以搜索文件内容。社区和论坛也很强大。我们对这个选择很满意。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://mindtouch.com/^0|Q|2|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I had the same dilemma of which wiki to use for a dev project a few months ago. We went with <a href="http://mindtouch.com" rel="nofollow">Mindtouch</a> due to the fact that it's free (Mindtouch Core), it has lots of great extensions, the design is modern and flexible, the file attachment and linking capabilities are comprehensive, and it can search through file content. The community and forums are also strong. We've been very happy with the choice.

blocks|key|965257|text|我会选择特拉克，因为它将Wiki与问题管理和版本控制结合在一起，这对于软件开发来说是非常完美的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|965258|从他们的地盘，|965259|Trac是一个用于软件开发项目的增强的wiki和问题跟踪系统。Trac使用了一种基于web的软件项目管理的极简方法。我们的使命是帮助开发人员在远离障碍的同时编写优秀的软件。Trac应该尽可能少地强加于团队既定的开发过程和策略。|blockquote|965260|因此，它是为软件开发团队构建的。|entityMap|0|LINK|mutability|MUTABLE|url|http://trac.edgewall.org/^0|4|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I would choose <a href="http://trac.edgewall.org/" rel="nofollow">Trac</a>, which is perfect for software development since it combines Wiki with Issue Management and Version Control.

From their site,

<blockquote>
 Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies. 
</blockquote>

So it is built for software development teams.

blocks|key|965379|text|我想这取决于你的要求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|965380|我所见过的绝对最好和最容易设置/使用的方法是：|965381|TiddlyWiki|offset|length|965382|文件中的wiki。它使用JavaScript来做所有的事情，并且工作得很好！|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tiddlywiki.com/^0|0|0|0|A|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

I think it depends on what your requirements are.

The absolute best and easiest to set up/use that I've seen is:

<a href="http://www.tiddlywiki.com" rel="nofollow">TiddlyWiki</a>

A wiki in a file. It uses JavaScript to do everything and works great!

blocks|key|2795977|text|您应该考虑一下PBWiki，它具有非常好的界面，对于小型项目、用户级访问控制和更有趣的功能是免费的。(更别提我自己也用过了，取得了很好的效果。)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2795978|PBWiki特征|entityMap|0|LINK|mutability|MUTABLE|url|http://pbworks.com/|1|http://pbworks.com/content/biz%2Bfeatures^0|7|6|0|0|0|8|1^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

You should consider <a href="http://pbworks.com" rel="nofollow">PBWiki</a> which has a really great interface, is free for small projects, user-level access controll and more fun features. (Not to mention I've used it myself with great results.) 

<a href="http://pbworks.com/content/biz+features" rel="nofollow">PBWiki Features</a>

blocks|key|2796013|text|XWiki是一个专业的wiki，具有博客、强大的权限管理、LDAP身份验证、PDF导出、全技巧等企业功能。它还包括高级表单和脚本引擎，使其成为基于数据的应用程序的开发环境。它具有强大的可扩展性功能，如页面脚本、插件和高度模块化的体系结构。有关更多信息，请参见完整的功能列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://xwiki.org/^0|0|5|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

<a href="http://xwiki.org" rel="nofollow">XWiki</a> is a professional wiki with enterprise features such as Blog, strong rights management, LDAP authentication, PDF export, full skining and more. It also includes an advanced Form and scripting engine making it a development environment for data-based applications. It has powerful extensibility features such as scripting in pages, plugins and a highly modular architecture. See the full feature list for more.

blocks|key|2796242|text|光明绿色有一个免费的版本，他们的应用程序3个用户。他们专注于Scrum和精益看板，但是这个工具对于一般需求管理也很有用。您可以在这里注册一个免费帐户：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2796243|https://signup.brightgreenprojects.com/plan/Free|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Scrum_%2528development%2529|1|http://en.wikipedia.org/wiki/Kanban|2^0|U|5|0|12|2|1|0|0|1C|2^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]|O|$5|H|I|J|C|$K|E]]]]

Bright Green have a free version of their application for 3 users. They focus on <a href="http://en.wikipedia.org/wiki/Scrum_%28development%29" rel="nofollow">Scrum</a> and lean <a href="http://en.wikipedia.org/wiki/Kanban" rel="nofollow">kanban</a>, however the tool is useful for general requirements management also. You can sign up for a free account here:

<a href="https://signup.brightgreenprojects.com/plan/Free" rel="nofollow">https://signup.brightgreenprojects.com/plan/Free</a>

blocks|key|2796371|text|我们是dokuWiki的大粉丝，它是灵活的，简单的(没有数据库，但如果你想的话你可以)，并且有很好的特性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dokuwiki.org/^0|3|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

We are big fans of <a href="http://www.dokuwiki.org" rel="nofollow">dokuWiki</a> which is flexible, simple (no database but you can if you want) and have great features.

blocks|key|965288|text|比你选择哪个软件更重要的是确保你明白了你想用维基做什么。如果没有某种总体的意识结构，wiki很容易变得不可用。此外(虽然不是那么重要)，了解wiki的行为也是有意义的，因为它不是灵丹妙药：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|965289|http://www.wikipatterns.com|offset|length|965290|然后，您可能想作为管理员考虑一下您在wiki中寻找的是什么--例如，它们的脚本性有很大的不同，可能是twiki在上面(或者我很少有经验的汇合点)。另外，例如，MediaWiki完全适用于大多数开放环境，它们的ACL特性不太好。另一个方面是，这些可能太重和复杂，你想做什么，你应该做一个wiki，就像一个与商业售票系统的集成。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wikipatterns.com/^0|0|0|R|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]]]

Almost more importantly than which software you choose is to make sure you understand what you're trying to do with the wiki. Without some overarching conscious structure a wiki easily becomes unusable. Also (though not as crucial), it makes sense to learn some about the behavior with wikis, because it is no silver bullet:

<a href="http://www.wikipatterns.com" rel="nofollow">http://www.wikipatterns.com</a>

Then you may want to consider as an administrator what you are looking for in the wiki - there is significant difference in for example how scriptable they are, probably with twiki ending up on top (or confluence which I have little experience with). Also for example MediaWiki is completely adapted for mostly open environments, their ACL features are not that good. Another aspect is that these may be too heavy-weight and complex for what you want to do, and you should make do with a wiki like the one integrated with the trac ticketing system.

blocks|key|965302|text|不久前，我也曾支持过类似的尝试，并选择了MoinMoin。它是免费的，非常容易设置和配置。最后，我用这个引擎管理了几个wiki实例--每个开发团队都在处理不同的项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://moinmo.in/^0|K|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I championed a similar endeavor a while back and chose <a href="http://moinmo.in/" rel="nofollow">MoinMoin</a>. It's free and very easy to set up and configure. I wound up managing several wiki instances with this engine - one for each of the different projects the development team was working on.

blocks|key|965334|text|我建议PmWiki。它非常简单，不占用资源，并且使用文件来存储数据。我把它拿起来20分钟就跑了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/PmWiki^0|3|6|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I'd suggest <a href="http://en.wikipedia.org/wiki/PmWiki" rel="nofollow">PmWiki</a>. It's very simple and doesn't really hog on resources and uses files to store data. I got it up and running in about 20 minutes.

I am trying to set up a wiki/management system for a software project and keep getting confused by the myriad of options available.

I have seen <a href="http://twiki.org/">TWiki</a> and <a href="http://plone.org/">Plone</a> before, which bill themselves as enterprise level components. Would they be better to use than something like, say, MediaWiki?

What are some other suggestions for wiki/management software?

For a software development project, what is the best type of wiki?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正试图为一个软件项目建立一个wiki/管理系统，并不断被各种各样的可用选项所迷惑。我以前见过TWiki和普隆，它们将自己定义为企业级组件。它们会比诸如MediaWiki之类的东西更好地使用吗？对于wiki/管理软件，还有什么其他的建议？

问对于软件开发项目，什么是最好的wiki类型？
EN

回答 25

Web Applications用户

Web Applications用户

Web Applications用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于软件开发项目，什么是最好的wiki类型？EN

回答 25

Web Applications用户

Web Applications用户

Web Applications用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于软件开发项目，什么是最好的wiki类型？
EN