Overview

Aurora currently offers three options for editing your content-rich areas:

• Plain-text editor - Used for editing content in it's 'source' format, e.g. HTML, JSON, etc.
• WYSIWYG editor - Used for simple 'word-processor' like content management.
• Page Builder (Beta) - Used for complete page layout editorial, but currently in its experimental Beta stages of development.

Content Switcher

Default Editor

📘

Aurora allows you to select a default editor to apply to your content management experience. Access this setting in the Aurora Backend under Store > Settings > Aurora > Editor. See the settings called "Default content editor" and select the option you would like to use by default.

When set, this will be applied to any content editor UI when adding new items, i.e. when editing an exiting item, the default does not get applied, instead relying on the selection made for that item when it was added or last edited.

Switching Content Editors When Editing

Once you begin to edit an item in Aurora, e.g. a Product or Snippet, you can select the editor you would like to use for that item. Once selected, all fields for that item that use an Editor will be changed. Once saved, Aurora will remember what you selected for that item for future and this can differ from one item to the next (e.g. product to product can have a different setting).

When switching between editors, it can be possible to change the content in ways the editors do not like. Please bear this in mind when creating content in the Page builder (for example) and then editing it in the Test-area.

Front-end Styles

📘

To improve your experience of using the WYSIWYG Editor and Page Builder, Aurora allows you to load your Front-end CSS files into the editor previews!

Access this setting in the Aurora Backend under Store > Settings > Aurora > Editor. See the settings called "Import CSS Files" and enter each CSS file you would like to include on a new line.

When set, both the WYSIWYG Editor and Page Builder will apply the CSS from these files to the previews they generate in real time. For example:

/templates/example.com/_css/template.css
/templates/example.com/_css/bespoke.css
/templates/example.com/_css/home.css