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: |
...
Anchor | ||||
---|---|---|---|---|
|
...
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 |
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.
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.
...
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.
...
Strict access level recommendation for any tag type(s): Only show attendees content that matches their access level.
Flexible access level recommendation for any tag type(s): On: 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
|
...