wiki

I recommend you try Federated Wiki [0]. To test out its editing process: 1. Go to: http://fed.wiki.org/view/how-to-wiki 2. Once you're there, click the "wiki" word down in the grey footer. A checkmark will appear next to the word "wiki." 3. Double-click a paragraph and edit. Ctrl-s saves. The page you edited will gain a yellow halo. The yellow indicates that your changes are only being saved in your browser's local storage for now. (If you have your own site and are logged in, changes will be saved on the server.) I run my own Federated Wiki (fedwiki) server. You can also just run it locally (which I do sometimes). It requires nodejs. I was a bit fussy with my server setup and have lighttpd as reverse proxy (I think that's the correct terminology) and 'supervisor' as nodejs babysitter, but most (all?) of that is not strictly necessary; fe

Yesterday Bloomberg published a story [0] on internal tension in World Bank's development economics group. The submitted article is the internal blog of the Bank's chief economist Paul Romer (apparently mirrored publicly by him), which communicates some of his thoughts central to the conflict. It's fascinating to read his views on trust and communication applied to their work, originally for an internal audience and now shared. These seem like issues worthy of getting everyone worked up. Also, in the About page [1] he goes into his thoughts on how prose should work and how his approach to the blog embraces that, citing the living nature of Wikipedia as better system than "books in libraries" or "docs on drives" but one that doesn't scale(?). He advocates for text files and DVCS instead. He uses Jekyll to author his blog, although it sound

That said, there are also options to use databases for page storage on the back end: https://github.com/fedwiki/wiki-node.

Ok, maybe someone would want to check the Smallest Federated Wiki: https://github.com/fedwiki/wiki-node