I'm using this as a wiki for my entire company, the developers and I would prefer to edit pages in markdown, whereas most of the other departments are not comfortable with markdown and much prefer the WYSIWYG editor.
It would be very useful to allow each user to set which kind of editor they would like to use.
An additional feature that would make this improvement better, would be the auto conversion from HTML to markdown when editing a page in markdown mode.
I will also like to add that, students using the system would like to be able to add and edit equations, formulas and Graphs.
I suggest the inclusion of a suitable TinyMCE plugin for Math and Graph
@KTSCode Thanks for the suggestion. I did think about this while developing the markdown editor. My main issue is that there will be a loss of formatting between the two editor options. By nature markdown is very simple so will not fully support all features in the WYSIWYG/HTML editor. Would this potential loss/change of formatting when switching between editors be worth the benefit of per user editor settings?
@bridgeyuwa I'd consider that if there's a suitable high quality & maintained library we can use.
@ssddanbrown I think the loss of formatting would not be a huge deal in most cases. Maybe it is worth saving which type of editor was used last on each page and warn the user of potential formatting problems if the previous edit was made from WYSIWYG/HTML and the new editor's settings are set to markdown.
WIRIS is the best TinyMCE plugin I've come across. It's excellent for equations but lacks graph functionality. And its moderately maintained.. I think it should serve for a start http://www.wiris.com/en/solutions/tinymce
@bridgeyuwa Thanks for the suggestion but, After a quick look, that plugin does not provide a clear open source licence so cannot be incorporated into BookStack.
@ssddanbrown I agree with @Tybot204 it would definitely be worth it, and a simple warning dialog box or even a warning toast, would be enough to stop anyone from accidentally destroying formatting. The people who use markdown are usually developers or at least understand what potential harm could be caused.
I'm not sure if the license on this repository is OSS enough to allow it to be used, but it claims to preserve the HTML tags that do not have a markdown equivalent. _I have not tested it_
The main reason I created this issue is, because I often forget to change it back to WYSIWYG after editing pages and no one outside the Development Team will edit anything until it's changed back, even after I told them how to change it. I've had to stop using markdown mode and tell everyone not to use it, because if someone forgets to switch it back, or a 'WYSIWYG User' tries to edit it, at the same time, it makes them not want to since "it looks scary". I'm really trying to get everyone at the company to adopt the use of BookStack as our Wiki. It's only beneficial if everyone is willing and able to edit it.
Fixing this issue would allow the Development Team and I to use/enjoy the markdown feature. Without it having the markdown feature is useless to us.
Lastly I just wanted to thank you @ssddanbrown and everyone else who has contributed to this project, for providing me and my team with a great opensource way of sharing information and maintaining documentation.
I would also like to request this feature for similar reasons explained by @KTSCode. IMO it would be ideal to either limit the WYSIWYG editor to Markdown compatible formatting or try to preserve html formatting if necessary.
I'd prefer and WYSIWIG which writes markdown under the hood too.
It's nicer and easy to store in a database (most for search!)
I would also like to add my voice to this. I would much rather see a scaled down WYSIWYG that could match the markdown so that both could be used and I could implement use with my whole team.
I am coming across this more and more as we use it. We have guys that exclusively use markdown and guys that need wysiwg. Has this been worked in.
Just putting this here for review - https://nhnent.github.io/tui.editor/
License is fine but this obviously will not meet a lot of the stuff that we do with TinyMCE right now.
Hi all, any updates on this? We just started using it and we are very interested in per-user editor setup.
Right now most of the pages created by devs look like plain-text markdown pages due to the WYSISWY default editor (used by the rest of the employees) 馃槙
No real update right now, I've added some more recent comments more recently on a related issue: #369.
Please 'Thumbs-up' the original top post to show support for this feature as that's taken into consideration when choosing features for a release.
Would also love this, even as is
@ssddanbrown hello, any news on this ? any way we can help ?
@ssddanbrown alternatively would there be a way for developer to switch to a different editor for the Markdown (eg. have github style markdown for example).
I posted my suggestion already in a different issue, but because it is also relevant in this issue I will poste the link here:
https://github.com/BookStackApp/BookStack/issues/842#issuecomment-487932048
Hi, any chance this is being considered for any time soon? Let me know if we can help, there's a few of us from mh company waiting for it. Thanks
Most helpful comment
@ssddanbrown I agree with @Tybot204 it would definitely be worth it, and a simple warning dialog box or even a warning toast, would be enough to stop anyone from accidentally destroying formatting. The people who use markdown are usually developers or at least understand what potential harm could be caused.
I'm not sure if the license on this repository is OSS enough to allow it to be used, but it claims to preserve the HTML tags that do not have a markdown equivalent. _I have not tested it_
The main reason I created this issue is, because I often forget to change it back to WYSIWYG after editing pages and no one outside the Development Team will edit anything until it's changed back, even after I told them how to change it. I've had to stop using markdown mode and tell everyone not to use it, because if someone forgets to switch it back, or a 'WYSIWYG User' tries to edit it, at the same time, it makes them not want to since "it looks scary". I'm really trying to get everyone at the company to adopt the use of BookStack as our Wiki. It's only beneficial if everyone is willing and able to edit it.
Fixing this issue would allow the Development Team and I to use/enjoy the markdown feature. Without it having the markdown feature is useless to us.
Lastly I just wanted to thank you @ssddanbrown and everyone else who has contributed to this project, for providing me and my team with a great opensource way of sharing information and maintaining documentation.