A great place to post your ideas and vote on others so that you can let us know what is important to you.
Please take the time to register, and then share your detailed use case and how the proposed enhancements could provide value to your organisation.
We endeavour to provide an initial response to all ideas in a timely manner.
Our Experience Designers are always excited to talk to our customers about your experiences with the system. If you are keen to chat to them, you can easily book a short session with a member of the team right here.
PLEASE? PRETTY PLEASE? It's a super simple WYSIWYG plugin like TinyMCE or something. I know you know that already, and I imagine that you're terrified that many people will actually use it and get themselves into trouble, but I actually can spell HTML and reaaaaaallly need it. Maybe set it up for "power users" only? Maybe do like WordPress and hide it n a foldable menu?
This is a MASSIVE need for us. To the point where I will happily support donuts and beer is that's what greases the skids these days.
Thank you!
|
What is the business process you are trying to achieve?
Inability to apply CSS at a word or line level. Example, I want one word in a header to be purple, but I can't assign a Span to it. |
Thanks for providing this suggestion James.
I believe that my colleagues in the Professional Services team have already discussed this with you, but I wanted to ensure we provided a response here on the community forum as well.
To date, we have consciously taken the decision with product to not enable the "edit HTML source" capability of the rich text editor, and I wanted to share the key reasons with you.
Firstly, the transition between what you see in the WYSIWYG editor and the HTML view is generally not as clean as one would like within these rich text editor controls. The HTML tends to get negatively impacted via that round trip, with the result often being that what you end up with back in the visual view isn't quite what you started with. These changes are often subtle, but we've tried to avoid our users needing to chase down these quirks.
Another key consideration is that the HTML tags which are outputted on the website are carefully controlled when the pages are rendered. This is important to ensure that the pages remain as responsive and accessible as possible. By allowing users to edit HTML source, we run the risk of ending up in a situation where the page appears to render fine in the page builder in the content management system, but behaves differently when rendered on the site itself.
With this in mind, we are not planning to enable this feature on the rich text control. However, I'm mindful of your need to be able to apply additional styling to the content on your pages. There are a couple of approaches that can be employed to achieve that outcome.
Firstly, you can utilise a code block rather than a text block within the page editor, and enter the HTML mark-up directly into code block editor. Alternatively, you could use the text editor, and override the existing styling of a supported tag such as "strong" in the CSS. To do this, you would need to apply a custom CSS class to the text block via the "advanced" option on the edit dialog.
Our team are happy to work with you to assist you to achieve the optimal outcome within current page editor functionality.
--
Steve Oxley
Product Manager