mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Give the possibility to choose between Markdown or TinyMCE at the page creation #392
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 @hotgeart on GitHub (Aug 4, 2017).
We use BookStack to write the doc at the office and some people are developpers orthers aren't so ofc the dev want to write in MK and the others don't want to learn MK.
So the choose can be specific to the page and not a global option ?
@fredericmohr commented on GitHub (Aug 4, 2017):
I personally would prefer it per book or chapter (or having all three options but allowing admins to disable some of them for their users).
If everyone can change the setting per page, it might lead to huge mix in HTML/MD pages, but per book it shouldn't be such a problem. Dev-Books can use MD while others use TinyMCE.
Just my 2c.
@ssddanbrown commented on GitHub (Aug 4, 2017):
Just for reference, Somewhat related to #119 and #369
@ssddanbrown commented on GitHub (Apr 24, 2022):
PR #3387 has now been merged, which allows switching of editor type 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.
The code for this has been merged and is targeted for the next feature release (Likely v22.04).
I'm going to close off this issue as being covered by this change. While this issue specifically states "at page creation", I wouldn't really want to prompt a user with this choice before page creation since it would add an additional barrier & step. Having this within the page edit view achieves the fundamental request of this issue with pretty much the same ease/speed from an end-user perspective.
@fredericmohr (If you're still using BookStack 5 years later 😅) This addition does work at a book/chapter level but does come with permission control, A new role-permission has been added to control users that are able to switch the editor which I hope helps your scenario.
@fredericmohr commented on GitHub (Apr 24, 2022):
I am still using and still loving BookStack. In fact, I just moved all my content from an old installation to a new server. Exciting to see this change happening. Thanks a ton for all your great work! 😊👍
From: Dan Brown @.>
Sent: Sunday, April 24, 2022 15:21
To: BookStackApp/BookStack @.>
Cc: Frederic Mohr @.>; Mention @.>
Subject: Re: [BookStackApp/BookStack] Give the possibility to choose between Markdown or TinyMCE at the page creation (#458)
PR #3387https://github.com/BookStackApp/BookStack/pull/3387 has now been merged, which allows switching of editor type 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. https://user-images.githubusercontent.com/8343178/164977916-9c8beee1-8578-43cd-b877-accb55e97fb6.mp4
The code for this has been merged and is targeted for the next feature release (Likely v22.04).
I'm going to close off this issue as being covered by this change. While this issue specifically states "at page creation", I wouldn't really want to prompt a user with this choice before page creation since it would add an additional barrier & step. Having this within the page edit view achieves the fundamental request of this issue with pretty much the same ease/speed from an end-user perspective.
@fredericmohrhttps://github.com/fredericmohr (If you're still using BookStack 5 years later 😅) This addition does work at a book/chapter level but does come with permission control, A new role-permission has been added to control users that are able to switch the editor which I hope helps your scenario.
—
Reply to this email directly, view it on GitHubhttps://github.com/BookStackApp/BookStack/issues/458#issuecomment-1107841075, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNOC7SI6QUA2L7XOBJ4CVTVGVDGJANCNFSM4DVVOZXQ.
You are receiving this because you were mentioned.Message ID: @.***>
@ssddanbrown commented on GitHub (Apr 25, 2022):
@fredericmohr Amazing! That's wonderful to hear.