Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Discussion based on these wireframes and the current implementation of the tool, as well as the questions listed here

Note: 

  • We don't have alternate modes in the design yet, working on speech to text, adding images, will eventually include video, ASL ...
  • A story summary is a short 1 or 2 line summary of the story


  • the TTS engine needs to know the language of the story in order to choose the appropriate voice (when activating "Listen to my story") - so choosing the language of the story needs to happen on the first screen
  • how does this relate to choosing the language of the interface? we can’t assume that the language of the interface is the same as the language the story is written in (especially when a user is translating a story)


  • Share vs save without sharing
    • Share = publish to collection
    • Save without sharing = store it but not publish it, maybe for editing

    • Upon save, goes to the story in its published form
  • Read another story like this
    • Finds another story with similar tags
  • Next story goes to next story, alphabetically
  • Is it better to have a search field at the top of the main screen?


  • how to handle/structure/create categories? 
    • easiest way is probably to require the user to choose a category or categories from a limited set for each story (like Youtube, except we needn't limit it to one category)
  • combine this with free-form tags to allow more flexibility in choosing descriptive and unique theme tags


  • Results page
    • If there's no summary provided, show the first couple lines of the story
    • Scroll through the results


  • should we allow users to edit their stories?
    • yes, both their own as well as allowing collaboration/remixing between users
  • how do we deal with translations and editing?
    • would have to use versioning to keep track 


  • probably want to have the original story text persist on the screen while doing a translation (rather than editing it directly in a single field as it's shown now)
  • what about starting with an auto-translation and then allowing editing from there? could be an option
  • want to be able to check and edit the auto-translations (even for single words or phrases such as theme tags)


  • should we provide translation as part of the authoring/editing environment at all? maybe better to just offer it in the story viewer
    • maybe “view in another language” offers translations that have been done manually only?
    • and/or auto-translations are dropped directly into an editing interface?


  • language drop-down - want to include an “other” option for any languages that aren’t on the list
  • we should include language locales too (i.e. Canadian English)


  • what about translating the theme tags?
  • or do we keep them as-is in the language they were added? 
    • we need to translate them to facilitate searches in multiple languages (or can users rely on the search engine searching through content and titles only?)
    • we can use auto-translate, but this is still problematic especially for multi-word tags and phrases




  • No labels