Attendees:
Daryl, Paul, Brian, Daniel, Michael

Notes from the call:
Continued focus on component editing screens using the wireframes produced after last weeks discussion. All agreed this is a major element of the authoring tool so vital we dedicate enough time and resource.

Discussed method and approach for component validation and field checks on save/preview of component. Main aim is to allow quick build and preview of component which would require adding default content to key fields but there was also discussion on adding holding text (Lorem ipsum...) to fields and placeholder images where relevant.

Auto populate and clear buttons were suggested for content but not settings fields. This idea was dropped for a more intelligent approach that would effectively achieve the same thing. Populating forms with default text could be misleading and irritating for users when editing. Suggestion was to populate on preview and/or publish but highlight that dummy content was being used and flag in a validation report.

Need to explore the use of filters and display options to show any fields with dummy content. These could also be used to show the validation errors and warnings.

Idea to lock settings based on user permissions was again raised.

Discussed what buttons should appear on the component editing screens: preview, publish, save, test, cancel. Agreed that we would want to keep the options minimal and only use save and cancel within component editing as the other functions of preview and publish were presented on the page structure screens.

Looked at a couple of examples of advanced filters and auto-complete search options within interfaces. Git Hub elegantly presents this type of functionality and we should explore these concepts within the Adapt authoring tool.

Current designs need a clear separation between filtering and display. Display options as per asset management wireframes (top right - thumbs, listings, preview etc), filtering options within left-hand side panel need additional designs, potentially using pop-out menus for advanced options.

Next Steps

• Continue to build wire-framed version of component editing and once complete invite wider community feedback.
• Vital we get a wide cross-section of feedback from technical and non-technical users.
• Consider concept of progress indicators within components.
• Outline changes to schema required to achieve the functionality being suggested.