Schedule:

Walkthrough of MVP and Wireframe

Participants:

Deborah, Nils, Paul, Ryan, Tony

 Making sure Content Developers. Designers, Developers are all happy with what is being prototyped and that all elements are being included/considered.

• Check Instructional Designers view on including extra things not included from developers point of view.

Ryan - Walkthrough of MVP and Admin User

• User Admin/Super Admin responsible for user creation/password reset and assign users a login (possibly there email address).
• Theme (CSS/Template files) will be created offline (by Developers) and uploaded (by Developers). Then Normal Users will be able to Select Theme.
• Debugging - login as user.
• Multiple themes for single Tenancy.
• Themes will control all colours etc in the output framework.
• Theme used to change the Layout ??
• Themes will be initially very simple & possibly minimal (with a view to adding other improvements in the future).

Ryan - Walkthrough of Normal User logging in

• Products probably listed from Latest Updated in descending order.
• Asset Manager possibly updated in the future to include Flickr, Twitter integration.
• Different views for Preview:
  • Print Preview - minimal styling with all on one long page.
  • Saving the package and linking to it to preview.
    • Live Preview - future enhancement.
    • Glossary/Search to span the full Course.

Paul - PDF Walkthrough

Attempts/Pass marks - where are these set ??

• ASSESSMENT: ??
  • Set at the Article Level
  • Only 1 type of Article, but this can contain different attributes.
  • Ties into tracking or just tracking everything ??
  • Possibly flag certain Questions/Components as assessment elements.
  • Quiz - need certain Score.
  • Update the Course while creating it at each element as needed and flag for assessment.
  • RESULT ARTICLE: ??
    • Not currently available but if it was created it would change User path - Go back if Fail, Continue if Pass.

Tony - Wireframe Walkthrough

• Initially very simple for New Users (add more features/functionality in future).
• Module Overview:
  • Add New Module/Edit existing Module/Import Module.
  • Page Overview: (Double Click on Module ^ to get here)
    • Old Sections are now Pages.  (Diagram here)
    • Old Pages are now Articles. (Diagram here)
    • Possibly make fewer Pages and more Articles.
    • Page Editor:
      • Opens in a new tab
      • Menu for Exit/Export and more in the future.
      • Layout drop down - result could potentially be controlled by Theme
      • Global Settings (for all Pages), Individual Settings (for specific Pages).
      • Add an Image:
        • Uploading from Desktop (first version).
        • Image Vault as a future enhancement.
        • Image Editor:
          • Set Ratios for image cropping (will always stay as a square or rectangle when resizing).
          • Page Editor:
            • Global Settings - Font Colour, Font Size, BG Colour, Opacity, Border Styles
            • Page Settings - Similar properties but specific to Individual Page.
            • Page Content Editor:
              • Change settings that were already set in the previous Editor (if needs to be updated while your working or something does not look correct with a colour).
              • Button - [[ + Article ]] - Add another Article below.

• • Button - [[ + Block ]] - Add another Block below.
  • Changing the Order will be done using a Drop Down:
    • 1... 2... 3... etc. Can be reordered by changing the Number (weight of the component).
  • Future enhancement - Drag and Drop functionality for changing the order or adding new components.
  • Components are Limited to 2 Side by Side (depending on the component).
  • Components will have set configurations: Full, Left or Right

Feedback from - 4th / 5th -11-2013.

• Annotate/Comment Mockflow.
• Please see attachments for first drafts of the ADAPT Builder MVP for both Admins and Editors.

Hi everyone,

During the time I've been working with Adapt on live projects (mostly styling/ui) I have often needed to quickly test things or find out some kind of information when fixing bugs. For example is the course menu showing the correct information on course completion?  Are the results screens showing the correct styling appropriate to the feedback?

I was wondering what everyone's thoughts were of building a test bench plugin for Adapt?  It could be enabled by setting a "dev" mode to true in the JSON config. This would bring up a panel that allows quick access to common tests, it could also show helpful information.

Some examples:

• Setting course/page to complete/not complete - a number of scenarios this could be useful
• Show Bandwidth - useful for planning the impact of media rich courses on the client's setup
• Show UserAgent details - catching stuff like ie9 going into ie7 compatibilty mode
• Quick Navigation - helpful for courses that have step-locked content
• Safe Mode - removes all CSS/images etc 

I think the test bench would also be quite useful for QA teams and supporting clients with issues.

I understand most of us here could use the console to test these things, but I think a tool to quickly test/view important information would be really useful.

Thanks

Sal

Good morning,

So here we are with HTML and it's ability to work on most devices. Kinda.

One discussion I'd quite like to open up is the browser spec for core Adapt. Currently as a company we support IE8 and above. I mention only IE8 as most of our mobile browsers/tablet browsers are of a good standard.

The reasoning behind just supporting IE8+ is so we can create beautiful content across all the browsers. The client has an expectation that whatever device they go on it should look the same. I'd disagree and find the idea of progressive enhancement a much more sustainable approach. Maybe IE6 and 7 don't have fancy stuff, instead you can still see the content and work through it.

I've tested Adapt in IE6 and IE7 - it works. Doesn't look pretty and some styling issues are a nightmare to fix.

After a few discussions with the team at Learning Pool, I've come to realise that we're claiming to create a platform that can deliver learning content across any device. So this means future devices but also older browsers.

Responsive content plays a big part of this. It enables us to create content based upon the width of the screen size. So really our platform should work on all future devices.

Let's not worry too much about the newer browsers and let's discuss the older ones. Firstly - anything below IE6 is not supported. I can safely make that claim because IE5- does not render content properly and has troubles with ajax requests. Not only that - they are not support by Microsoft and haven't been for a very long while.

So discussions start with how far are developers willing to work?

Does this benefit Adapt?

Does this benefit companies - I know that we have clients using IE6 and IE7 but we have another framework we could use.

Our initial thoughts on iOS devices and mobile devices tend to update more frequently so two versions back is ok.

Plugins for Adapt - do they need to have a browser supported attribute or should they all gracefully fall back?

Should the editor have the same spec? (I'm more on the verge of saying no to this)

From a discussion with Sven, we both agreed that a 'reasonable' spec would need to be agreed.

Would love to hear people input, especially project managers/ and learning designers as progressive enhancement will mean a significant change to the way we sell Adapt to clients.

Thanks,

Daryl