Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Special TextBlock component #69

Open
3 tasks
dafrie opened this issue Jan 25, 2021 · 0 comments
Open
3 tasks

Proposal: Special TextBlock component #69

dafrie opened this issue Jan 25, 2021 · 0 comments

Comments

@dafrie
Copy link
Member

dafrie commented Jan 25, 2021

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

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant