Skip to end of metadata
Go to start of metadata

Open Design Questions

  • How are categories assigned?
    • It seems like they're automatically added upon story submission/sharing
    • Could have user pick from a limited list when they create their story
    • Could have them curated by someone (labour intensive, time consuming)
  • How do tags differ from categories, functionally?
  • What does it mean to share a story? "Share my story" vs. "Save without sharing"
    • Is it like YouTube, public vs hidden?
    • "Share" could mean publishing it to the greater collection
    • "Save without sharing" could mean store it but not publish it, maybe for further editing before sharing
  • User/authoring/session management
    • User accounts?
    • Token given when story is added?
    • Collaboration?
    • What if a story is edited after being translated?
  • How should languages be represented for user input?
    • Drop-down box with a list of language codes
      • How do we decide which languages to list? A subset of all IETF languages codes?
  • What is searched?
    • Tags
    • Categories
      • Clicking one of the category names on the search page suggests this is an option
    • Titles
    • Content
    • Everything?
    • All of the above?
  • What is the initial view when arriving on the site?
    • Index of stories
      • Chronological?
      • Some other arrangement?

  • Translations:
    • How do we store which languages have had requests submitted for them, and how many times?
    • How do we notify a user when a translation they requested has been provided?
      • Should we?
      • goes back to the question about session management.
        • Would we store email addresses?
        • If a user returns to a story with their edit token, would it indicate that a translation was provided
    • How should languages be represented for the user?
      • A drop-down list with options and an optional text box that shows when they choose "Other..." from the list
      • Store the languages internally using one method such as IETF codes/BCP-47, e.g. "en-CA" or "zh-TW"
        • If the user chooses "Other", do we ask them for an IETF code? Can we expect them to know what that is?
      • Show a "friendly" readable name
        • in the language of the UI or in the language and script of the actual language?
          • i.e. for French, should it say "French" or "français"? "Japanese" or "日本語"?
          • possible issues with right-to-left script systems?
      • Could auto-detect the story's language (using an API) and then ask the user if that's correct
        • "Is your story in Spanish?" or similar
    • When the user is in the initial "Story Translation" context, what's the best way to indicate which languages are already implemented, requested and how many times for each?
      • Multiple translations or requests for a given language should be allowed
        • Should we allow requests for languages that have already been provided?
      • Perhaps this is more appropriate to show on the Story viewer context before they click "Translate this story"
  • Translations of the UI
    • Could make the message bundles for the UI public, so people could independently submit localisations of the UI
    • Perhaps a page with every message name listed along with those for the UI they're currently using, as well as empty text boxes for their new localisation (~30 messages)

Ongoing Design Discussion

  • No labels

1 Comment

  1. Dimensions of Inclusive Story Telling. 

    All diverse voices of a wide range of  human beings needs to be heard at all levels to facilitate their inclusion and participation in all activities .The dimensions of SJTK inclusive story telling provides guidance and justification for inclusion for all in story telling.The dimensions are ;

    1. Raising the voices of all especially those at the margins of the social, economic, political and cultural set up or sectors of the society.

    2. A wide range of ways of seeing,hearing and perceiving the world.There is no standard right way of telling a story.There are many ways of telling stories.Providing guidance through illustrations and demonstrations  is to facilitate people to tell their story in their own ways.

    3. Technology is a powerful tool for equalizer and filling in the inequality gap.Enabling all users to use online spaces such as  social media spaces enables them to raise their voices ,be included and participate in all activities.

    4. Sharing stories contributes to a positive change.Reflect on experiences,raise awareness on social injustices,modify behaviours of all actors,inclusion and participation for all.