Aristotle Page Editor/s

Is there any plans to enhance the WYSIWYG editors in Aristotle?
For instance, the current tool ribbon in the Home Page and Item editors only provides a limited set of font controls (eg Bold, Italic, Subscript and Superscript). It would be nice to gain some additional controls, such as Underline, Colour and Size - the later would be particularly useful when creating a heading within a shaded/coloured cell in a table.
The same could be achieved by directly coding via the Source function - however (I’ve discovered) such creativity cannot be saved, as they are bleached by security safeguards that Aristotle has put in place to ensure we don’t break anything.
Alternatively, can we gain access to the CSS set for a subsite in Aristotle? which would enable site wide controls over the way certain a component/div is displayed (eg H1 style could be set to a particular font size and colour, etc).
Supplementary question, can we control/restrict access to some or all of the editor functions?

Hi Col,

The reason we’ve selected bold, italics and underline is those are all styles that can be applied using standard HTML tags. This helps us use a limited set of the rich text capabilities of HTML to provide a safe ability to add styling, without impacting on the layout of the site (similar to what we do with this community site as well)

For us to add other styles, such as font colour and size we will need to add more general support for CSS styles - which could allow a user to change font sizes to the point that they break the layout or add text that doesn’t meet accessiblity guidelines.

To keep users within these standard boundaries, what we currently do is remove any HTML styling outside of it which is what is causing the errors you are noticing.

Rather than opening up advanced styling or direct HTML editing for all users, what we can do is investigate how to add extra privileges to the site that allow users to control different levels of the styling.

For example:

  • Basic editing (with the functionality)
  • Advanced editing (with fewer restrictions on styling)
  • Unrestricted editing (with no restrictions on styling, but an included disclaimer about dangers of direct HTML editing).

This would allow use to meet the needs of advanced users on an opt-in basis given by system administrators, without opening up the potential risk to all users.

I’ll speak with the team about adding this to our roadmap backlog and will give you an update once we’ve developed some mock-ups.

1 Like