Page Comparison

...

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?

...

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
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.

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

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

...