At the moment we have a way for a consumer of an editor to specify atto toolbar buttons for individual uses - for example a quiz question developer can specify individual editor buttons in atto.

This is a clear breach of component comms principles and we need a non-atto-specific way of doing this.

This was originally implemented by quen for the OU.

I think that there are a few good options to go for:

• implement editor presets for basic, and standard (and possibly advanced). These can be admin-configured but an individual consumer can specify an editor option of, for example, $options['layout:preset'] = 'basic';
• implement editor presets for different themes with possible fallbacks. For example a math-based question type may define a preset of $options['layout:purpose'] = 'math';. This may not work in all situations - for example a multichoice editor may have different content depending upon the content of the question (set by the teacher).

Hopefully Sam or timhunt have some ideas on how we can achieve this in a more sustainable fashion, and perhaps a better description of the use-case behind it (as it is not used in core).