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

We need full richtext features for our blog posts #396

Open
RachellCalhoun opened this issue May 2, 2024 · 0 comments
Open

We need full richtext features for our blog posts #396

RachellCalhoun opened this issue May 2, 2024 · 0 comments
Assignees

Comments

@RachellCalhoun
Copy link
Member

          Went with option two and gutted the features of the RichText Block. It's still beneficial to keep RichText Block for underline, italicized, bold, strikethrough, superscript and subscript text. 

The status of all elements can be seen on staging https://staging-djangonaut-space.azurewebsites.net/comms/elements/

Originally posted by @dawnwages in #164 (comment)

@RachellCalhoun RachellCalhoun changed the title We need full richtext features We need full richtext features for our blog posts May 2, 2024
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

2 participants