Skip to content

Beta Update

The first meeting of the Adapt Beta team happened on Thursday, May 17th and included a lot of feedback and questions.

The meeting was excellent, I wanted to thank everyone for participating — I know how busy you are. Your feedback, problems and even just random thoughts are astoundingly valuable!

Here’s a brief recap:

We discussed using Submenus in a course and when they might be appropriate (thanks Lanette!).
The short answer is: We’re not sure. There aren’t any visual differences between submenus and the main menu, so we all worried that this might confuse learners.
There is a future task for the development team to research if there is a way to add some visual differentiation to submenus. It’s a long-shot, but but worth looking into. This task will happen late-beta or shortly after launch.
Go to Page and Go to Menu Navigation
It was decided that the development team would attempt to create new components that would allow the authors to add a button that would take the user back to the menu or to another page. (Thanks for the suggestion Lanette!).
These components now have Asana Tasks (1, 2 — eBusiness Asana access required). While it is not currently scheduled, it is considered required for launch (if it’s possible to create).
We touched on the duration field for pages. This field is information only, and is not shared with the LMS and has no effect on the course or the learner.
The user’s guide has been updated to better reflect this information.
HTML Text seen in the page block on the Page Editor
Several team members noticed raw HTML code appearing on the Page Settings and/or Article blocks in the Page editor.
Results are preliminary, but after a bit of research, this appears to be Adapt Authoring protecting itself from potential malformed HTML.
The code can be safely ignored, as it appears correctly when editing the field (in the TinyMCE editor) and in the Course Preview.
If anyone wants the somewhat weird details, please let the development team know (it might be worth an article).
The idea of a Choose-Your-Own-Adventure was brought up (Thanks Rachel!).
While it is an idea we considered as a component, for now it seems that Adapt’s data structures are too rigid to allow for this type of component (adapt uses fixed arrays for data, CYOA’s need a dynamic tree structure).
However, this may not be the end for this component. Future Totara development plans to include the interaction and a UI to create them directly into Totara. The project team will evaluate whether we can invest the time bring this into Adapt.

Thanks again for everyone’s time! We look forward to more feedback and to seeing what everyone comes up with!