2 ms·
I like the spirit of it. For me, what would most give a wiki lightweight, efficient user experience is in-place editing, like a word processor. It's so much mor
by wolverine876 5y ago
I like the spirit of it. For me, what would most give a wiki lightweight, efficient user experience is in-place editing, like a word processor. It's so much more efficient - imagine the reverse, if Word required you to reload for every edit! In detail:
* In wikis I've used, editing requires 6 steps and 2 page reloads: 1) Find existing content/location on page (on pages that aren't tiny), decide what/how to edit. 2) Switch to edit mode (page reload, and lose my place). 3) Find existing content again. 4) Edit it. 5) Save (page reload, and lose my place). 6) Find new content and verify it.
* In-place editing, as imagined, would be 2.5 steps, no reloads (again, like a word processor): 1) Find existing content on page, decide what/how to edit. 2) Edit. 2a) Verify it.
The cumbersome nature of the current process consumes a lot of time (I'm a heavy user) and deters a lot of editing. I wouldn't even mind an 'in-place' mode change, where I didn't lose my place and didn't have to wait for a reload.
How difficult would that be? Does any wiki do it? I would be willing to help pay for its development, it would save so much time and also so much cognitive overhead.
- hales 5y agoTiddlywiki seems (from a technical perspective) a little bit closer to what you're imagining: https://tiddlywiki.com/ https://tiddlywiki.com/ Sadly it doesn't let you edit WYSIWYG, ie when you click "Edit" it still transforms the section back into monospaced markup script in a textarea. Theoretically it should be possible to change that, but I have not looked at the codebase. If you were to do this from the ground up you would probably: * Enable .contentEditable on the whole page (or at least sections like <main>) * Add a floating toolbar for formatting controls (and a save button) * Do the submit in javascript, so the page doesn't have to fully reload. * Possibly add a toggle edit button? Or would people be comfy being able to accidentally edit pages whilst reading (as long as they realise they have to hit "save" to make a change). This might ruin some people's navigation key shortcuts in their browser (eg users of Vimium). For personal or small-team use I could see this being good. For larger teams it would be a nightmare, as accidental edits would be common. The formal 3/4 step editing process has its problems, but it's a useful barrier against the tides. Alternatively you could stick to using MS Office/Libreoffice, set the view mode to "web" and hyperlink to subheadings as your navigation (instead of "pages"). If we wash our minds of the historical uses of word processors versus web browsers: this could be a very successful implementation for 1 user or a few users (on a network share).
- wolverine876 5y agoThanks for this! > Sadly it doesn't let you edit WYSIWYG, ie when you click "Edit" it still transforms the section back into monospaced markup script in a textarea. I actually prefer that; I didn't mention it because it seems like additional complexity that few besides me would desire. I'd rather edit using markup; it's much more precise. Heck, I could use an extention to add a Vim UI to the textarea and I'd be in heaven. > Possibly add a toggle edit button? I think that would be important in most circumstances, to facilitate a reading UI (including navigation, as you mention) and to prevent accidents and make editing more of a thoughtful choice. > The formal 3/4 step editing process has its problems, but it's a useful barrier against the tides. We could still have required preview steps, without waiting for reloads and losing our place on the page. > you could stick to using MS Office/Libreoffice, set the view mode to "web" and hyperlink to subheadings as your navigation (instead of "pages"). I thought about that. Several problems, mostly related to complexity of word processing: Over many years and edits, word processing documents become a mess; text-based wikis are invulnerable. Also, it's harder to create simple structured documents, with proper formatting, in word processors (and things become a mess again), where wikis again are very simple - just use the header/subheader syntax. And word processors are paper page-oriented regardless of mode, which is more complexity and also an absurdity in a wiki.
- jimbosis 5y agoI recommend you try Federated Wiki [0]. To test out its editing process: 1. Go to: http://fed.wiki.org/view/how-to-wiki 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; fedwiki can just run on its own. [0] https://github.com/fedwiki/wiki https://github.com/fedwiki/wiki EDIT: Clarity.
- wolverine876 5y agoThat's fantastic, and it's UI seems very efficient. Thank you!
- Brian_K_White 5y agoIn-place editing is only good for private documents. For publicly viewable documents I absolutly want the edit-preview-edit-preview...publish steps. Trying to optimize those away is optimizing the wrong thing. It's like parking your car in your bed room to make it more convenient to get from the bed to the car.
- wolverine876 5y ago> For publicly viewable documents I absolutly want the edit-preview-edit-preview...publish steps. If you want to preview before publishing, you could still do it with edit-in-place. > In-place editing is only good for private documents. Many wikis (including some described in the OP) are private or only used by a few people. Wikipedia is an exception, not the rule.
- Brian_K_White 5y agoThat's like saying many papers are used for private documents.
- wolverine876 5y agoI think you are overlooking the use of personal knowledge bases, including wikis.
- Brian_K_White 5y agoWhat are we even talking about any more? The post was about some wiki sofware. Of course some people may use it in a private context. So what?
- galacticdessert 5y agoTrilium Notes might be what you are looking for. Very very pleasant https://github.com/zadam/trilium https://github.com/zadam/trilium