curl -O http://enterprisewiki.co/bin/app.min.js
  uglify -b | vim -

Looks like they're using Showdown for Markdown functionality, sharejs for concurrent editing, node-browserchannel for async communication... Or, maybe Closure's BrowserChannel?

I would love to see an end-to-end "here's how we built this" blog post for this kind of project. Very nicely done!

I'm very excited about fixing wikis, and I'm really impressed to see that OP has some very similar ideas about it.

Because of this, I found it worthwhile to burn 1-2 hours to de-minify his Javascript, which mostly required figuring out what all his inlined JS libs are.

https://gist.github.com/4321959

To save you a click, here are the JS files he uses:

https://github.com/EightMedia/hammer.js/blob/master/jquery.h...

http://code.google.com/p/rangyinputs/source/browse/trunk/jqu...

https://github.com/jeresig/jquery.hotkeys/blob/master/jquery...

https://github.com/EightMedia/hammer.js/blob/master/hammer.j...

Modified version of http://code.google.com/p/jquery-elastic/source/browse/trunk/...

http://code.google.com/p/webapptools/source/browse/trunk/wat...

https://github.com/coreyti/showdown/blob/master/src/showdown...

https://github.com/coreyti/showdown/blob/master/src/extensio...

https://github.com/coreyti/showdown/blob/master/src/extensio...

https://github.com/coreyti/showdown/blob/master/src/extensio...

http://sharejs.org/channel/bcsocket.js

http://sharejs.org/share/share.js

http://sharejs.org/share/textarea.js

you could have just asked :) see the post below - it outlines the libs used, the rest probably aren't the best choices anyhow, took 2 days to put this together so it's hardly an example to follow :)

share.js (and its dependencies - redis, socket.io), prettify, showdown, etc. it's really simple, not much to write-up I'm afraid :)