Background[edit | edit source]

  • Learning experiences (XPs), or XPs, are a core element on the LRNG platform.
  • An XP is an activity that asks the learner to take specific action and demonstrate a particular learning outcome.
  • XPs are the container for learning activities, including both local events and online interactions.
  • XPs lead to Digital Badges.
    • Digital XPs are virtual experiences that can be done by way of remote learning. No personal contact and face-to-face meeting is needed with a Digital XP.
    • Local XPs are experiences that need to be done, in part, with a face-to-face setting. A Local XP can be part local and part remote.

Insights[edit | edit source]

Details for buiding XPs[edit | edit source]

  • Title
    • Choose a concise name that is appealing to learners and meaningful to potential consumers. Limit of 70 characters.
  • Banner Image (or video)
    • Choose an attractive banner that is engaging for learners. This important image offers the first impression of this XP in the Discovery Feed. Image must be JPG, GIF or PNG, 2880x1400 pixels or larger, up to 5MB. Note: if you choose a video, you will have to add a thumbnail image. The thumbnail image will show up in the Discovery Feed instead of the video, which will only be viewable on the XP Detail page.
  • Description
    • Briefly describe the experience in a way that is engaging to learners. Use the description to get at the meaning and value behind the experience. Use the “Submission Requirements” section to define specific required outcomes.
  • Resources
    • One by one, add links to external Resources that might be helpful to learners in completing the experience. For example, in order to submit a reflection on the Percy Shelley poem, “Ode to the West Wind,” one would need a link to the resource: the text of that poem, or a book containing it.
  • Submission Requirements
    • Describe the evidence a learner must submit to complete this XP. When possible, phrase this as an invitation to participate or chance to provide proof of an experience, not as a to-do list. Bullets are recommended here. If necessary, be specific about what type of media format you would like for the submission (e.g., picture, video link, text, file upload, URL, etc.). If your XP is a local event and can be completed through attendance, you could simply require the learner to snap a photo of their ticket or presence at the event.
    • Note: Keep in mind that learners will only be able to submit a single piece of evidence per XP.
  • Interests
    • Choose the one interest category that best reflects the badge you are creating. Note that these are not intended to be academic subject areas, and are meant to align learning opportunities with the interests of youth. If there isn’t a perfect option, choose the one that is closest. The list is intended to be a high-level view of interest areas, not a comprehensive tagging and sorting mechanism. In the near future, tags and/or sub-categories will provide the option to more discretely sort your content.
  • Age Appropriateness
    • Choose between the 13+ or All Ages options to concisely describe your content and align it with COPPA and other common age regulations OR choose a custom age range to specify your target audience. We recommend publishing content and experiences with as broad an audience as possible.
    • Choose the level that best fits how you expect learners to engage with your XP.
  1. Meet Up: Based in friendship practices; little to no production
  2. Play Up: Exploring new tools; production likely, but not polished
  3. Level Up: High demands for learner production and feedback from mentors
  • Estimated Duration
    • Define your best guess for how long in hours and minutes the average learner will spend completing this XP. (This will not be surfaced to learners, but will factor into reporting and goal tracking.)
    • Note: For local XPs, make sure to add additional details as necessary, including date, time, location, registration information, price, URL, and contact info.

Links[edit | edit source]

Community content is available under CC-BY-SA unless otherwise noted.