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

More formatting options in the default Rich Text editor? #441

Open
stevenyang1011 opened this issue Oct 13, 2020 · 11 comments
Open

More formatting options in the default Rich Text editor? #441

stevenyang1011 opened this issue Oct 13, 2020 · 11 comments
Assignees
Labels
feature-request stale Used to mark when there was no activity for a set period of time

Comments

@stevenyang1011
Copy link

stevenyang1011 commented Oct 13, 2020

Is there any plan or road map to support more formatting in the default Rich Text editor? For example superscript <sup> html tag or the subscript <sub> tag?

@lindelleric
Copy link

And to add to this: It would be nice if you could set text-align on text..

@suevalov
Copy link
Contributor

suevalov commented Nov 4, 2020

@stevenyang1011 @lindelleric The team will be working on Rich Text updates next Q1 and we might add these new formatting options or make customization easier. We'll keep this issue open and close once we have new Rich Text capabilities.

@srounce
Copy link

srounce commented Nov 4, 2020

Being able to add items to the embed dropdown would be amazing too.

@DanweDE
Copy link
Contributor

DanweDE commented Nov 17, 2020

@srounce Could you please elaborate on what kind of items you'd like to be able to add to the embed dropdown?

@stevenyang1011
Copy link
Author

One of the issue I ran into customising the Rich Text Editor is the validation. When I add more plugins to render superscript and subscript tags, the validation gives an error unless you enable all the formatting options on the content model.
image

I could not find documentations on customising the formatting options to add more for my subscript and superscript plugins. The workaround I used is to enable all so the validation passes and turn off certain formatting option by modifying my extension to not render the plugins.

@th1nkgr33n
Copy link

Just for note there is a discussion going on inside the slack community about this topic.
The problem to add new nodeTypes (not marks) is that there is a deeper validation inside contentful you cannot bypass.
https://contentful-community.slack.com/archives/CBYTK7T9S/p1626664817229800

@github-actions
Copy link

Marking issue as stale since there was no acitivty for 30 days

@github-actions github-actions bot added the stale Used to mark when there was no activity for a set period of time label Aug 14, 2022
@OzzieOrca
Copy link

This appears to have been already implemented by #1280 and contentful/rich-text#391:
Screenshot from 2023-06-15 17-48-19

If you still aren't seeing the feature, edit your content model and enable the field formatting options:
Screenshot from 2023-06-15 17-49-10

@github-actions github-actions bot removed the stale Used to mark when there was no activity for a set period of time label Jun 16, 2023
@github-actions
Copy link

Marking issue as stale since there was no activity for 30 days

@github-actions github-actions bot added the stale Used to mark when there was no activity for a set period of time label Jul 16, 2023
@ghost
Copy link

ghost commented Jan 8, 2024

Is there a way to customize the field options for custom apps?

@github-actions github-actions bot removed the stale Used to mark when there was no activity for a set period of time label Jan 9, 2024
Copy link

github-actions bot commented Feb 9, 2024

Marking issue as stale since there was no activity for 30 days

@github-actions github-actions bot added the stale Used to mark when there was no activity for a set period of time label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request stale Used to mark when there was no activity for a set period of time
Projects
None yet
Development

No branches or pull requests

8 participants