Versions Compared

Key

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

Page Properties

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
  •  A CSM who has had trouble explaining module customization to a picky/highly custom client in the past?
  •  Leon (just the recommended tags section)

Review deadline

Notes for reviewers

...

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

Copy and paste the form below

I’d like this module to…

Show these content type(s): This field is required. The rest are optional.

  • With this session status:

  • With these static tag(s):

  • And apply this dynamic tag settingWith these dynamic tag type(s):

  • With these dynamic access levels:

Then sort it all by:

...

Anchor
pull
pull
1. Pull content types (required)

...

Expand
titleold- delete?

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
These are custom tags that you create then apply to each piece of content that you’d like to appear in the module. Layout tags are the simplest way to group content. Usually, they 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
These

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

Static tags

You can narrow down any content type to show only content that has specific tags applied to it. Note that every attendee will see the same content, even if they didn’t select Leadership as one of their interests. If you want to show attendees personalized recommendations, see the options below.

(tick) Choose any profile, layout, and/or access level tags

Profile tags are any tags attendees select when they create their profile. For example, an onboarding question might ask about their interests, with multiple options like Leadership and Design. Any of these tags can be applied to related content and pulled into the module.Note that every attendee will see the same content, even if they didn’t select Leadership as one of their interests.

If you want to show attendees personalized recommendations, see the options below.If the module you’re creating isn’t related to any profile tags, you should create a new layout tag. Usually, a layout tag simply matches the module title or page title. For example, if a module is titled Featured Sessions, create a Featured Sessions tag and add it to each piece of content that you’d like to appear in that module.

Access level tags are… You have content behind a ticket paywall. You want to group it together in one module.

Dynamic

...

tag types

Recommend content with dynamic tags. Each attendee will see different content depending on their tags or access level.

...

(tick) Flexible content recommendation for any profile tag type(s): Show attendees content related to the tags they selected from a specific tag type. But this limits attendees options less by still showing them content outside of that tag type.

...

(tick) Strict access level recommendation for any tag type(s): Only show attendees content that matches their access level.

(tick) Flexible access level recommendation for any tag type(s): On: Same as above but access level. Don’t understand

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 

...