UIOptions is currently extremely hard to configure in order to handle different options. Anastasia has explored some of the requirements and it has been found that we require to touch the codebase in upwards of 6 places in order to successfully integrate a new option. Some of these problems were also seen in the work on the "content simplification demo".
An "ant" (so named after a discussion in Toronto during July) encompasses all of the aspects necessary to deal with a new option in one "component". These are, presentation, persistence, and activity.
Presentation governs an interaction with the user to configure the option.
Persistence enables the user's set value to be persisted to a profile.
Activity honours the option's value in a particular context (for example, transforms a web page).

This work is necessary for further embedding of UIOptions in other contexts (FLOE content) as well as GPII profiles/preferences work