mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Switch between Markdown and WYSIWYG when editing pages #681
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pommetjehorlepiep on GitHub (May 16, 2018).
Desired Feature:
I'd love to be able to switch between Markdown & WYSIWYG when editing pages.
Much better than: go into the settings, change the editing mode and edit page(s) and once finished go back in settings to set mode back again.
@ffub commented on GitHub (May 18, 2018):
I would also like this. This functionality is handled well in a number of static site editors such as https://www.siteleaf.com/
@ssddanbrown commented on GitHub (May 19, 2018):
Thanks for opening this feature request.
This is very closely related to #119 and #458.
@ffub Have you seen any more complex editors that do this? Many I've seen are really built markdown-first so are fairly limited to just the core markdown formattings options. Just something that includes tables & text alignment and possibly custom formats.
@ffub commented on GitHub (May 26, 2018):
Realistically, switching between WYSIWYG and Markdown will mean storing the
file in the latter.
Toast UI allows for tables and code blocks.
I think a limited set of semantic elements and a storage format such as
Markdown is a benefit. It keeps pages from ending up full of junk HTML copy
and pasted from webpages and word processors.
The only elements that I think are handled poorly by Markdown are images. I
pretty much always want to add a caption to an image, and the
element is a really clean way to handle them in running text.
On 19 May 2018 at 15:25, Dan Brown notifications@github.com wrote:
@NickeZ commented on GitHub (Jun 11, 2018):
XWiki allows the author of the document to switch between markup formats in a lossy way.
@JHenneberg commented on GitHub (Apr 30, 2019):
The TOAST ui editor looks realy promising.
Markdown Wysiwyg Editor - Productive and Extensible
Live Preview, Scrolling, Syn, Auto indent, Syntax highlight
It looks also very similar to the currently used one. You can edit either in markdown or in the WYSIWYG.
https://ui.toast.com/tui-editor
@tlnagy commented on GitHub (Jul 14, 2019):
This would be amazing. I think I'll have a much easier time convincing my group to use the markdown version of the wiki if it included some WYSIWYG features. Right now there's a trade-off: portability in markdown mode and discoverability/convenience in WYSIWYG mode.
@GammaGames commented on GitHub (Jun 24, 2020):
I've actually used toast in projects, it's very good. I have the option to switch between the WYSIWYG editor and the regular markdown editor so it's easy for anyone to use how they want.
@kayvanaarssen commented on GitHub (Nov 24, 2020):
This would be awesome. We use this in our Wordpress KB as well
@Dalarialus commented on GitHub (Jan 19, 2022):
I'd really like to see this happen as well. I think that the ability to switch between markdown and WYSIWYG during editing would really help to balance functionality with ease of use.
@ssddanbrown commented on GitHub (Apr 24, 2022):
PR #3387 has now been merged, which allows switching of editor type (If role permissions allow) from within the editor.
The editor type is then saved against the page itself, and uses the system setting as a default.
A preview can be seen here.
This isn't as instant as front-end switching (As per something like ToastUI) since we swap editor implementation depending on choice and we need to show a confirmation due to fundamental impacts of changing the editor. But it should be a lot faster and friendlier than current approaches, to cover most fundamental needs of this request.
There are two choices when moving from WYSIWYG to Markdown:
The code for this has been merged and is targeted for the next feature release (Likely v22.04), So I'll therefore close this issue off.