This guide helps you _________
Build your own module in two steps |
|
How to choose heading
[VISUAL DIAGRAM of this plus this equals this, and/or content being “pulled” with arrows]
First, pull content into the module using one or more methods:
You can use more than one method. Example: Pull all Library content, then only select the ones with specific tags.
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: |
1. Pull content types (required)
First, decide which type of content you’d like to appear in the module.
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.
Your choices are:
Sessions
You must also specify the session type: Main stage, Panel, and/or Breakout.
In-person sessions
You must also specify the session type: Main stage, Panel, and/or Breakout.
Library (also known as On-demand)
Exhibitors (also known as Partners)
Speakers
Courses (also known as Tracks)
Lessons
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.
2. Narrow down the content selection (optional)
After choosing a content type, you’ll often want to narrow it down so the module is focused on a specific topic, availability, or personalized recommendation. For example, instead of showing any course, a module might only show courses about “leadership”.
Why? Narrowing down content is particularly useful when you have a lot to share with attendees. Instead of trying to fit all content into a single module (like a large grid), create multiple modules on the same page! Then give each module a different focus so attendees can discover content in a variety of ways.
Use one or both of the methods described below.
Session status
If you pull Sessions or In-person sessions into the module, you can narrow it down to sessions with a specific status. A session’s status changes over time as it goes from Upcoming, to Live, to Past.
Your choices are:
Live now
Upcoming and Live now
Past and Live now
Note that the module will appear empty whenever there aren’t sessions with the specified status. For example, you might not choose Live now if your event has a lot of downtime in between live sessions.
Tags
You can narrow down any content type to show only content that has specific tags applied to it.
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.
Make personalized recommendations using tag types
Recommend content with dynamic tags
To recommend content based on profile tags that attendees select:
Choose any profile tag type(s)
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 Leadership
, and another will only see content tagged Design
.
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.
The require_some_preferred use case… encourage users to see other content to broaden their horizons.
To show attendees content based on access level:
Access level tag type: to only show attendees content that matches their access level
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?
[EXAMPLES OF TAG COMBOS - show 1 here and link to the prebuilt ones for more]
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
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