Re:Etsy’s experiment with immutable documentation
by bjoernm on Friday December 14, 2018 @05:28AM
(#18679829)
Have a look at Nuclino (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.
Re:Etsy’s experiment with immutable documentation
by closeparen on Thursday December 13, 2018 @06:57PM
(#18677261)
Google Docs. Has comments, too.
Re:Etsy’s experiment with immutable documentation
by forapurpose on Friday December 14, 2018 @12:07AM
(#18678606)
How 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.
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