4 ms·
> the use of slack significantly lowers the transaction cost of adding the documentation. In a wiki, where there is a certain level of quality expected ... The
by forapurpose 8y ago
> the use of slack significantly lowers the transaction cost of adding the documentation. In a wiki, where there is a certain level of quality expected ...
The wikis I've used also have slow editing interfaces because they have separate read and edit modes. Does anyone know of a modeless wiki, which probably means one that allows you to edit-in-place?
The problem with modes is that to edit something on a sizeable page you must,
1. Load the page in read mode
2. Read/search to locate the spot on the page where your edit goes, read the context around it, and plan the edit.
3. Load the page in edit mode
4. Read/search to locate the spot on the page where your edit goes
5. Type your edit
6. Reload the page in preview mode (a form of read mode)
7. Read/search to locate your edit and verify it
8-?. Repeat steps 5-7 until your edit is correct.
N. Reload the page in read mode.
Compare to a modeless wiki:
1. Load the page in read mode
2. Read/search to locate the spot on the page where your edit goes, read the context around it, and plan the edit.
3. Edit until satisfied
- closeparen 8y agoGoogle Docs. Has comments, too.
- forapurpose 8y agoHow easy and efficient are other wiki functions, such as creating hyperlinks between documents, creating new documents, and a simple, structured style system? Last time I looked at it for these purposes, Google Docs failed in those areas.
- bjoernm 8y agoHave a look at Nuclino (https://www.nuclino.com https://www.nuclino.com), essentially a real-time wiki for teams. We're eliminating modes the way you describe in order to speed up the workflow. It supports edit-in-place, changes are automatically saved and you can collaborate in real-time (like in Google Docs), but you also have core wiki features like easy linking and consistent styles.