Landscape Screenshot - Ideas to use this without it being too small.

Dec 06, 2016

I am working on a course that helps people understand a report and how to work it. The report is not sizable, so it's tiny text and it's a long landscape screenshot. I need to explain each column in a story sized 720x540 - using the landscape screenshot will not work. 

 

Any ideas on how to maybe break it up or creatively review it?? I'm sort of stumped at the moment! 

 

Thanks!

3 Replies
OWEN HOLT

Don't break it up. Leave it big and beautifully detailed and let the user pan around it using their arrow keys. You can use a relative motion path and variables to achieve the effect and hot spots to reveal the info the learner needs.

See this post for ideas: https://community.articulate.com/discussions/articulate-storyline/how-to-pan-the-screen-left-and-right-using-a-slider-and-motion-paths

Dave Ferguson

Two suggestions (or one suggestion and a thought)

First, building on Owen's idea: assuming there are sections in the report (like a group of columns that relates to one type of information), can you show a reduced-size version of of the report, or even a stylized small version, as The Big Picture, using those sections as part of a brief overview?

  • This area (sync with box or colored highlight or what have you) gives you the customer information....
  • This area (new box/highlight) has order-history details...
  • This area (yet another box/highlight) contains credit and payment history...

Second, the thought, even though I'm just guessing:  depending on how people work with the report, maybe you can use different desired results as a way to explain its parts.  E.g., one thing people do is find a customer (in column B) and check the most recent shipment (in column H). At that point I don't care much about columns C through G.

If you have several such ways that people put the report to work, then maybe this outcome focus ends up covering all the parts, rather than simply going in the alphabetical order of the columns. 

This discussion is closed. You can start a new discussion or contact Articulate Support.