You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed, the approved chapter of book v2 seems to include much more "language switching" within free flowing text, rendering the proposed approach of dragging text components down for each switch (as implemented in the current editor) quite user unfriendly. Also, there seems to be much more traditional text formatting going on than in the previous book.
We therefore decided to discuss/implement a wyswyg based special component for this workflow. The idea is, that the flow of the editor is not stopped and we do the necessary conversions to the component type structure upon loading and saving.
Proposed next steps
Make some UI mockups on how we could approach this
Find a suitable, react friendly wyswyg editor. Req's: Needs to support mapping of "custom tags"
Decide on whether to use backend or frontend for the mapping logic
The text was updated successfully, but these errors were encountered:
Context
As discussed, the approved chapter of book v2 seems to include much more "language switching" within free flowing text, rendering the proposed approach of dragging text components down for each switch (as implemented in the current editor) quite user unfriendly. Also, there seems to be much more traditional text formatting going on than in the previous book.
We therefore decided to discuss/implement a
wyswyg
based special component for this workflow. The idea is, that the flow of the editor is not stopped and we do the necessary conversions to the component type structure upon loading and saving.Proposed next steps
wyswyg
editor. Req's: Needs to support mapping of "custom tags"The text was updated successfully, but these errors were encountered: