Posted by Fernando-Basso on
URL: https://discuss.asciidoctor.org/Creating-an-in-place-editor-wiki-app-using-Asciidoctor-tp6350p7419.html

Hey Dan,

I also don't think hiding the source code is a good idea. What I “advocate” is having an “inline preview” which allows one to have less cognitive dissonance because one does not need to keep looking back and forth from source do preview pane and vice-versa (and having to find the precise spot where the content was changed in the preview pane), but always making it possible to see the underlying markup whenever one wants, similar to what happens in org-mode, which hides a link markup, but shows it again when there is a missing "[" or "]", and hides it again when the syntax for that link is "finished/concluded".

In Typora, when you place the cursor inside an inline `piece of code`, the backticks are displayed, and when the cursor leaves that piece of text, the preview is displayed instead. The same for links and other markup.

In Zim, we have to _edit_ the links in a popup dialog. That is not what I think should happen (for links or any other type of markup). On the contrary, the user should have to properly type the markup, and when it is done, then the preview hides the markup and displays the preview. When the user enters a piece of text which contains markup, there should be a way to edit the markup in-place.

What I like the most in Zim is the *navigability*. The tree view for the files on a given wiki, and the TOC that can be floating or placed on the left or right, the @tags!. It is very _navigable_ and very _searchable_. OK, I realize this is a wiki software. Yet, I can only imagine how freaking cool it would be to have Zim/wiki-like features with the AWESOME Asciidoctor as the underlying markup language.

I was probably not very precise and clear as I would like to be, but I think it gives a better idea of what I have in mind.

Best,
Fernando