Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
Then sort it all by: |
...
Usually, you only need one type. But you can choose multiple. A common example of multiple content types in a module is Session + Library content. This module would offer attendees a mix of live and on-demand content.
Choose one or more content types: |
Sessions |
You can stop here if you’d like! The next steps are optional. Note that if you don’t sort (step 3), the module will by default show content with the most recent release date first.
...
Expand | ||
---|---|---|
| ||
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: Layout tags Profile tags You create these custom tags. They’re topics or interests. Attendees select from these tags during onboarding. Access level tags |
...
Expand | ||
---|---|---|
| ||
Options: Strict content recommendation for any profile tag type(s): Only show attendees content related to the tags they selected from a specific tag type. People will only see the tags they selected in their profile setup. For example, if the module pulls interest tags, one person will only see content tagged with Note that if someone didn’t select any tags for that type, they’ll see content with any tag. For example, if they didn’t select interests, they’ll see content about any interest. 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. For example, if some of your sessions aren’t related to interest tags at all, they would still show up in the module. This option is best when you want to make personalized recommendations but also want to encourage attendees to discover new things. Strict access level recommendation: Only show attendees content that matches their access level. Flexible access level recommendation: Same as above but access level. Don’t understand |
Anchor | ||||
---|---|---|---|---|
|
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
Pretty sure these aren’t for modules
|
...