I would love it if the Rich Text fields in Prismic supported multiple levels of indentation.
- Here is a parent item
- Here is a child item
- Here is a grandchild item
One of the following three behaviors would be necessary:
- Allow for indenting with tabs or spaces
- Add buttons for indent/outdent like what Google Docs has
- Add a markdown toggle for the rich text fields (similar to NetlifyCMS or Strapi)
There is no button to indent and I cannot find any keyboard combination that will allow it. Surprisingly I can't find any mention of this lack of functionality on this forum or elsewhere on the internet.
Issue that it solves:
Nested lists are a requirement for me, and having to use slices for this is not acceptable. There are several cases where I have a Rich Text field inside of a repeatable group within a slice, so there is no option other than breaking it into a separate Custom Type with a Content Relation. Again, this is not acceptable. I can deal with no native table support, but this one is essentially a blocker for my team to uptake the Prismic product.
Hello Alex, welcome to the community!!
This would be a really cool thing to have in the editor. I'm going to add it as an open feature request and if/when we have news about this feature being taken care of, we'll inform it here.
Right now there are two workarounds you could try:
You could use Markdown syntax. This of course would be a hacky option, but it's an alternative if you have a small list.
Use the Rich Text labels. You can create labels for multiple levels of indentation (e.g. "
list-level-2", etc.). This will apply a CSS class, which you can then use to give different amounts of margin. This could at least give you the appearance of nested lists. This option won't generate semantic HTML so It'll be only for UI porpuses in the writing room.
This is being tracked as an open feature request.
If you have another use-case for this feature, you can 'Flag' this topic to reopen. Please use the button to show your support for the feature and check out our Feature Request Guidelines.
Has anything changed in terms of support?
The work-arounds won't work for ordered nested lists as they are just cosmetic changes, but have no impact on numbering/alpha counting, like required in this example:
Hello @peter2, we have no news just yet.
We'll update this same thread when we have updates.
It's been nearly 6 months since the last reply here and we're coming up on the 2 year anniversary of this request. Any traction on nested lists in the editor?
Hey Frank! Thanks for the note. I've added it to our feature request page. What's new - Prismic, I nudged the team to let us know where this particular feature stands. I'll report back as soon as I have an answer for you.
In the meantime, I'd love to learn more about you and what your building. Would you mind heading over to this month's introductions thread and sharing a bit about yourself? You can find it here: Updates and Introductions: October 2022
Any update? I was also unable to find this one on the "What's New" page that you linked to. Can you share a direct link to it so I can track it's progress?
Hey @mike_g, we don't have news about this feature.
I've fixed the link, now it redirects to: What's new - Prismic
Thanks for the reply. I'm still not seeing anything on that page about this feature request. @erik.israni stated:
I've added it to our feature request page
Hey @mike_g, the progress page displays only the features we're currently working on. That's why new features don't appear there.
I've been testing this out for my company, but this feature is why I'll need to stay with my current CMS.
Wanted to share this with you so you know why it's a deal breaker for us to switch right now.
Bumping this thread, our blog does have a heavy use of this feature, I'd really like to avoid tricky workarounds, it's not user friendly for our editors.
Jumping on as well. Our users have to go back to our copy editors and ask them to rewrite sections to not use nested list items. This is common usage and causes friction.
Can't believe such a simple feature is not provided. Honestly Prismic RichTextEditor is the worst part in the whole CMS, makes me want to use WordPress to have a sane editor.
Is this going to ever happen? ...after three years? 100% agree with the comment above Prismic RichTextEditor is the worst part in the whole CMS. This kind of issues makes the prismic UX one of the worst in the whole headless market.
Hopefully it can be included in the new page builder??
As you may have seen we’re currently working on rebuilding the entire editing experience, and we are excited to share that we have our first alpha release. You can sign up to our waitlist and read more about it here
We want to clarify upfront that the first release will not include nested bulleted lists. This rebuild was an essential first step, laying a robust foundation that will enable us to iterate quickly and add new features in the future.
You can, however, expect some enhancements to the UX of our Rich Text Editor in this initial release. We will make sure to provide an update in this thread as soon as we have a timeline for when we will start working on nested bullet lists.
Thank you for your patience and understanding