Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties
Know which layouts are best for which content. Be able to pick one quickly and visually. Then if needed-- get into the details to know which elements can be configured
  • This is part 1 of 2. The second doc will cover all options for pulling and sorting content.

  • And we'll also be making a list of "prebuilt" modules so clients don't have to look at all this detail if they don't want to.

    Status

    Status
    colourRed
    titlenot visible to public
    Status
    titledraft
    (went thru all with nelly, started refining, got thru session status)

    Type

    explanation/reference

    Reader

    Clients / CSMs

    Reader goal

    Decide how to pull and sort content for a module, most likely coming from one of these mindsets…

    • They have a specific idea (use case) in mind – “Can I do this?” If they are tech/design savvy they might look at this on their own. Otherwise, they might ask a CSM, “can I do this?” and the CSM would look at this doc to find the answer.

    • Or they/CSM have a template or prebuilt module that they want to adjust. “I want to change this default. What are all my options?”

    They do NOT want to think about how it all works on the back end. They are focused on use case.

    Learning goal: Understand all parts of how content is pulled and sorted. Be able to fill in the “formula” with their choices and hand it to the CSM/Config team

    Contributors

    Nelly

    JUNO version

    Reviewers (check the box when you’re done!)

    •  Scrilla
    •  Travis
    •  Renae

    Review deadline

    Notes for reviewers

    This guide helps you _________

    ...

    Then, sort the content. This step is optional. If you don’t, it defaults to release date descending, most recent first.

    Some kind of copy and paste “formula” <<< actually maybe just visualize this formula above. Copy/paste doesn’t achieve a lot and it’s just repetitive?

    Must do

    Optional

    Sort content (optional)…

    Content bucket(s): ____

    + Session status: ____ + Tags: ____

    + Sort by: ____

    ...

    You can narrow down any content type using tags. Optional. You can pick one or multiple tags.

    If you don’t specify tags, any content from the bucket can be pulled into the module. If you do specify tags, only content that has that tag applied to it will appear in the module.

    Choose one or more tags:

    (tick) Layout tags
    You create these custom tags. They usually match your site’s page or module titles. For example, if a module is titled Leadership, you can make a Leadership tag and add it to each piece of content that you’d like to appear in that module.

    (tick) Profile tags
    You create these custom tags. They’re topics or interests. Attendees select from these tags during onboarding.

    (tick) Access level tags
    if you want content to be “locked” to users without permissions/tickets/etc. It will appear as locked. Use cases: want to advertise stuff for upsell OR just simply keep content locked from specific users

    • Recommend content/matchmaking/dynamic

      content changes per person. require users to have the tag in order to see it

      • add_users_tag_types []

        • Recommendations or locked content.

        • you choose the tag type (i.e. “interests”) and it will recommend content with interest tags that match what the attendee selected (i.e. “food“ and “sports”)

      • require_some_preferred_tags_of_type:

        • Recommendations or locked content where you want to encourage users to see other content they didn’t buy tickets for or to broaden their horizons.

        • need use case / example for this, don’t understand

      • SHOULD I TIE THIS IN ONLY WITH PROFILE TAGS?

    ...

    Anchor
    sort
    sort
    3. Sort the content (optional)

    Optional, Only pick 1

    If you don’t choose a sort, it defaults to release date descending (most recent first.)

    Sort by… GROUP THESE OR ADD DESCRIPTIONS FOR USE CASES?

    • Release date (ascending=most recent is last, or descending=most recent first)

      • Not just for sessions. For example, a library content page might not become available until a specific date.

      • when it’s viewable, which is usually well before the session starts, so people know it’s happening and can add it to their schedule.

    • Start date (ascending=most recent is last, or descending=most recent first)

      • Only sessions

      • when the session actually begins

    • Alphabetical

      • by title or speaker’s first name

    • Numerical (ascending or descending)

      • use it if the first character in the title are numbers. Example: 1 Session 2 Session

      • note that it won’t sort letters. Example: Session 1 Session 2 will not sort in numerical order

    • Random

      • different every ime you reload the page

    • Popularity - Tag score then date <<confirm that. scrilla said “prob” in a comment

    Warning

    Unsure if these are for modules/what they are

    • 1 = sort num responses descending 

    • 5 = sort children descending 

    • 6 = sort children ascending 

    • 12 = sort day and month ascending 

    • 13 = sort rotate every four hours 

    • 14 = sort rotate every hour

    • 16 = sort string option1 

    • 17 = sort string option2 

    • 18 = sort string option3 

    • 19 = sort match against score 

    • 21 = sort child ascending2 

    • 22 = sort content descending2 

    • 100 = sort pinned tag 

    • 101 = sort bucket tag ascending 

    • 102 = sort getty special 

    • 103 = sort tag order 

    Pretty sure these aren’t for modules

    • 10 = sort rank descending 

    • 11 = sort rank ascending 

    • 9 = sort action completed 

    • 23 = sort most completed action 

    • 24 = sort least completed action 

    ...