Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen
Feedback: HTML blocks should be optional/customizable
Gepostet 30. Aug. 2024
I understand and appreciate the purpose of the HTML blocks, but the implementation of them should be optional and/or customizable.
Use Case:
We provide article outlines that non-tech-savvy authors can easily copy and paste into new, blank articles. These outlines come pre-structured with all the necessary formatting—headings, tables, tabs, placeholders, etc.—allowing the authors to focus solely on adding content.
We do NOT want these headings, tables, tabs, placeholders, etc. to be within HTML blocks. The use of WYSIWYG is absolutely critical here.
Relates to this documented breaking change
5
3
3 Kommentare
Sabine Hanna
Agree, the HTML blocks have already caused a lot of frustrated contact from my users and a lot of extra work for me trying to fix articles for them. This is not a feature I would normally use and not having control over it is very annoying.
2
Patrycja Walencik
Erin McGarry thank you for your detailed feedback. We are working on improving New Editor to align it with customers expectations. I will let you know when we solut HTML block issue.
2
Daniel Hoult
I agree. Writers in our team are frustrated that the HTML blocks behaviour causes more work rather than enabling shortcuts.
Patrycja Walencik I read when using unlink on an HTML block it will “remove unsupported markdown”. What exactly does this mean? We use this option and then an iframe line displaying html content is removed which is not what we want.
0