[Feature Request]: support full WYSIWYG/markdown compatibility back and forth #2644

Closed
opened 2026-02-05 04:42:24 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @mchaptel on GitHub (Feb 7, 2022).

Describe the feature you'd like

Right now, pages using WYSIWIG are encoded using html. This means they cannot be later modified using markdown.

It would be better if WYSIWIG generated markdown under the hood, and that markdown was used to render the pages. This would ensure a complete back and forth compatibility between the two edit modes and not restrict edit mode to the way the page was created.

Describe the benefits this feature would bring to BookStack users

Different users have different preferences for editing modes, and the fact that this selection blocks half the users whichever way is chosen is detrimental to the cooperation of the teams.

This change in implementation could be transparent for WYSIWYG users and benefit all.

Additional context

No response

Originally created by @mchaptel on GitHub (Feb 7, 2022). ### Describe the feature you'd like Right now, pages using WYSIWIG are encoded using html. This means they cannot be later modified using markdown. It would be better if WYSIWIG generated markdown under the hood, and that markdown was used to render the pages. This would ensure a complete back and forth compatibility between the two edit modes and not restrict edit mode to the way the page was created. ### Describe the benefits this feature would bring to BookStack users Different users have different preferences for editing modes, and the fact that this selection blocks half the users whichever way is chosen is detrimental to the cooperation of the teams. This change in implementation could be transparent for WYSIWYG users and benefit all. ### Additional context _No response_
OVERLORD added the 🔨 Feature Request:cat2:🐈 Possible duplicate labels 2026-02-05 04:42:24 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Feb 7, 2022):

Hi @mchaptel,
This has already been requested in #842, with #119 and #458 being closely related. Therefore I'm going to close this off as a duplicate.

@ssddanbrown commented on GitHub (Feb 7, 2022): Hi @mchaptel, This has already been requested in #842, with #119 and #458 being closely related. Therefore I'm going to close this off as a duplicate.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#2644