2 ms·
Thanks 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 text
by wolverine876 5y ago
Thanks 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.