❓10 Common Questions: Part 6 ❓

Have you ever wondered what questions other customers are asking? Wonder no more! We’ve rounded up some of the most asked questions below.

Missed our other Common Questions? You can check out 1, 2, 34, & 5 here!

Q: What are the available Default Date Range options?

A: The available date ranges are: Today, This Week, Next 30 Days, Next 3 Months, Next 6 Months, and Next 12 Months. Here’s how you can update your DDR:

  • Navigate to to the Admin Dash > Settings > Platform Settings > Appearance
  • Select one of the options in the Default Date Range drop down
  • Save Changes

The above options are exclusive to our Emphasis theme. If you’re using our Legacy theme, the Default Date Range options are as follows: Today, This Week, and the Next 30 Days.

Q: When is it appropriate to use a Conference?

A: Conferences are not repeated and the “conference” is the event with optional sessions to be attended within the event. Use a Conference if you need to:

  • Host a one-time event that requires sessions (ex: open house/orientation)
  • Host an overnight event (ex: dance-a-thon)
  • Handle ticketing and registration as a whole (ex: 1 ticket for 3 dates)

Q: Can I set registration on a per-session basis for a Conference?

A: Yup! The Register functionality is exactly the same in Conference Sessions as it is for standard events. The only difference is that you’re setting up registration/tickets on a per-session basis as opposed to on the overarching event.

With this in mind, you’ll just have to navigate to the Edit a Session page in the Admin Dash > click the Tickets & Registration tab > click + Add Ticket or Create your first ticket

Q: How do I get notified that events are awaiting approval in the Pending Queue?

A: If you’d like Admins to receive notifications that there are pending events, you can add their emails to the Pending Digest Email field via Admin Dash > Settings > Platform Settings. This email is sent once daily and includes all pending events in the queue.

Please note that the Pending Digest is all encompassing. This means if an Event Admin is, say, Allowed to Lectures & Presentations and they receive the Pending Digest email, they will see events assigned to all other Classifications listed in that email. However, once they login and access the Pending Queue, they will only be able to see and moderate events that include their Allowed Classification(s).

Q: How can Event Admins (without publishing privileges) view/edit their events while waiting for approval?

A: When an Event Admin (without publishing privileges) submits or edits an event, it will go to the Pending Queue to be reviewed by another Admin. While events are in the Pending Queue, here’s how these folks can access/edit them:

  • Navigate to the homepage > click the user menu dropdown > Dashboard
  • Scroll down to Activity Feed > Pending Events
  • Click the event
  • On the Event Details Page, scroll to the Event Tools section at the bottom
  • Select Admin Event Editor to edit via the Admin Edit an Event Form
  • Upon saving changes, the event will remain Pending until it’s approved

Q: What happens to events after they’re rejected?

A: Here’s how the Rejected functionality works:

  1. Admin Rejects an event (with or without a Rejection message) in the Pending Queue
  2. The event becomes Unpublished & the Event Owner will receive an email notifying them of the rejection
  3. The Event Owner will be able to navigate to the event, where they will see a rejection pop-up
  4. From here, they can make edits and resubmit their event to the Pending Queue for approval

Q: When a feed the source deletes an event, will it be automatically removed from Localist?

A: If an event is deleted from the feed source, it will not automatically be removed in Localist. This is because it is impossible for Localist to determine whether the event has been deleted/canceled or if the event is just not present in the feed. In this case you will need to delete the instance at the feed source and in Localist.

Q: How can I use Localist to send mass emails to our community?

A: Our internal tool, Bulletin, allows you to create, manage, and send newsletters directly from your Localist platform. 

If you aren’t already providing a newsletter that highlights events then we’ve got you covered. Check out our Bulletin LocaList to learn more about this feature here!

Q: Can I change fonts and button colors to match our organization’s brand in a Bulletin Campaign?

A: Sure can! Here’s how you’ll update a Bulletin Campaign’s CSS:

  • Navigate to the Admin Dash > Bulletin > Campaigns
  • Click on the desired Campaign > Edit Content & Layout (top bar)
  • Select one of the components 
  • In the Editing Component, click Edit Component in Theme Editor
  • Once in the Theme Editor, select the Stylesheet file under Default
  • From here, you can change the default colors/fonts between lines 9-36
  • If you need to add additional CSS, you can do so between the <style></style> tags
  • Save Changes

Please note: Making small edits to the HTML/CSS of a Bulletin Campaign (like colors and fonts) should typically be fine. However, too many HTML/CSS changes can cause email softwares to display the content differently.

Q: How can I easily find events I’ve created in the Admin Dash?

A: Upon logging in to the Admin Dashboard, you’ll see a Manage Events section where you can find all of your Pending, Upcoming, and Recent events:

🗣️ 8 Ways You Can Participate in the Localist Admin Community 🗣️

Curious about what goes on behind the scenes with other Localist customers? Want to share what cool things you’re doing with Localist?

The Localist Admin Group, powered by LinkedIn, is a space for you to ask questions, share ideas and connect with other customers to swap insider tips with our community of Localist experts.

 

To get started, choose a topic below and either:

1) Share your unique experience and insight OR

2) Post a question for the community to answer

1. Admin Training Tips

  • What methods did you use to teach new Admins about the platform?
  • How do you continue to support Admins after training?

2. Internal Workflows

  • What tools do you use to communicate with Admins/your calendar team?
  • How do Admins coordinate with each other?

3. Feature Leveraging

  • What criteria do you use to determine if an event should be Featured/Sponsored?
  • What criteria do you use to determine if Channel is required?
  • How do you finalize Widget Template designs and placement?

4. Branding/Channel Customizations

  • How did you do…?
  • Has anyone done…?
  • We implemented.., here’s how:

5. Success Stories

  • What worked well to boost community/audience engagement?
  • What worked well to boost Department & Group engagement?

6. Launch/Promotion Tips

  • Do you have a sample calendar announcement you can share?
  • What’s the most creative way you’ve promoted Localist?

7. Integrations & Tools

  • Has anybody ever integrated with X platform/tool?
  • What concerns or heads up should we know when integrating with X platform/tool?

8. Events Your Team is Attending

  • Are you attending a conference?
  • Are you attending a webinar?

🎨 10 Cool Things You Can Do With the Theme Editor 🎨

Localist’s Theme Editor houses your platform’s HTML where you can customize how event data is presented. The template language is Liquid.

Please note that the images below are using our Emphasis theme. If your platform is using our Legacy theme, you can certainly still apply these styles to your calendar as well, but the code/steps provided may differ. Want access to Emphasis? Learn more about upgrading here!

 

1. Google Translate

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2 ) Open the Global Site Shell file under Wrapper at the bottom of the theme file list

(3) Add the below code directly under <meta name=”mobile-web-app-capable” content=”yes”>

(4) Save Changes

<div id="google_translate_element"></div> <script type="text/javascript">
function googleTranslateElementInit() { new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element'); }
</script> <script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>

Note: If you’re using a SILK Wrapper with our Legacy theme, you’ll add this in the <head> of your wrapper HTML file.

 

2. Static Featured Listings

Instructions

 

Step 1: HTML

(1) Navigate to Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Shared Among Multiple Views, select the  _featured_section file

Remove lines 1-17 and replace it with the following code:

{% for event in featured_section.events limit:3 %}
{% if forloop.first == true %}
<div class='em-carousel-slide'>
<div class='em-slidecontent'>
<div class="em-item em-card em-card--carousel">
<div class="em-list_tags">
<a class="em-card_tag">Featured Event</a>
</div>

(4) Remove lines 81-86 at the bottom of the file

(5) Paste the following code in its place:

<div class="featured-area-second-level event_list_component" style="padding-top:30px;">
<div class="featured-area-card featured-lower-two-cards em-card-group-featured em-card-group--medium">
{% else %}
{% render_event_item event %}
{% endif %}
{% endfor %}
</div>
</div>

(6) Save Changes
 

Step 2: CSS

(1) Navigate to Settings > Platform Settings > Appearance > Edit Settings for your Active theme

(2) Click the Custom CSS tab & drop the following code in the box:

.featured-lower-two-cards.em-card-group--medium {
grid-template-columns: repeat(auto-fill, minmax(450px, 450px));
}

.featured-lower-two-cards {
display: grid;
grid-gap: 2.5rem 2.1875rem;
justify-content: center;
margin-bottom: 4.25rem;
}

(3) Save Changes

 

3. Color Coded Event Types + Cards

Instructions

 

Step 1: HTML

(1) Navigate to Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Shared Among Multiple Views, select the  _event_item file

(3) Swap out line 3 with the following code: 

<div class="em-card{% if event_item.sponsored %} sponsored{% endif %} em-event-{{ event_item.event_id }} em-event-instance-{{ event_item.id }} {% for tag in event_item.event_types limit:1 %}{{ tag | downcase }}{% endfor %}">

(4) Swap out lines 51-55 & 64-68 with the following code: 

{% unless event_item.event_types == blank %}
{% for tag in event_item.event_types limit:1 %}
<a class="em-card_tag {% for tag in event_item.event_types limit:1 %}{{ tag | downcase }}{% endfor %}">{{ tag }}</a>
{% endfor %}
{% endunless %}

(4) Save Changes
 

Step 2: CSS

(1) Navigate to Settings > Platform Settings > Appearance > Edit Settings for your Active theme

(2) Click the Custom CSS tab & drop the following code in the box:

.em-card.EVENTTYPE {border-bottom: 5px solid #HEXCODE;}
.em-card .em-list_tags .em-card_tag.EVENTTYPE {background-color: #HEXCODE;}

* Swap EVENTTYPE with an actual Event Type’s name. For example, if you have an Event Type named Workshop, you’ll swap “EVENTTYPE” with “workshop” in the CSS selector.

(3) Save Changes

 

4. Adding Dept/Group/Tag to Event Cards

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Shared Among Multiple Views, select the  _event_item file

(3) Add the following code under {% end if %} on line 43:

TAGS
{% unless event_item.tags == blank %}
<div class="tag">
{% for tag in event_item.tags limit:1 %}
<a class="em-link" href="{{ tag.event_search_url }}">{{ tag.name }}</a>{% unless forloop.last %}, {% endunless %}
{% endfor %}
</div>
{% endunless %}
GROUP/DEPARTMENTS
{% unless event_item.groups == empty %}
<div class="em-event-meta-data-groups">
{% for group in event_item.groups %}
<a class="card-group" href="/group/{{ group.urlname }}">{{ group.name }}</a>{% unless forloop.last %}, {% endunless %}
{% endfor %}
</div>
{% endunless %}
OTHER FILTERS
{% unless event_item.types['event_audience'] == blank %}
<div class="em-event-meta-data-groups">
<p class="host">AUDIENCE:</p>{% for type in event_item.types['event_audience'] %}
<a class="card-audience" href="{{ type.event_search_url }}">{{ type.name }}{% unless forloop.last %}, {% endunless %}</a>
{% endfor %}
</div>
{% endunless %}

* What is underlined, event_audience, will depend on what Filter Family you’d like to include and how you have it named. For example, “Target Audience” would be [‘event_target_audience’] or “Topic” would be [‘event_topic’]. 

(4) Save Changes

 

5. Large Event Cards by Default

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Search Results & Month Views, select the file Search Results Page Shell

(3) Remove card_size:settings.card_size on line 253

(4) On lines 282 and 297, replace the {{ settings.card_size }} with big so it looks like <div class=“em-card-group em-card-group–big”> on both lines

(5) Save Changes

 

6. Submit an Event Component Customizations

Instructions

 

Step 1: HTML

(1) Navigate to Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Channels, select Submit Event Button

(3) Drop the following snippet below the already existing button code on line 10:

<br>

<a class="em-button em-secondary em-big em-event_button" href="https://localist.com">

Button Language Here

<i class="fas fa-long-arrow-alt-right"></i>

</a>

(4) Save Changes

Note: You can customize the Submit an Event Component’s header/description text  in your homepages Channel Layout Editor.

 

Step 2: CSS

(1) Navigate to Settings > Platform Settings > Appearance > Edit Settings for your Active theme

(2) Click the Custom CSS tab & drop the following code in the box:

.em-event_banner {

display: block;

text-align: center;

 }


a.em-button.em-secondary.em-big.em-event_button{

justify-content: center;

}

.em-event_banner .em-event_banner-content{

margin-bottom: 20px;

}

(3) Save Changes

 

7. Global Submit an Event Component

Instructions

 

Step 1: Channel Layout Editor

(1) Navigate to Content > Channels > select Edit Layout for your homepage Channel

(2) Click the “X” next to the Submit an Event component > Ok

(3) Save Changes

 

Step 2: HTML

(1) Navigate to Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Wrapper, select _footer

(3) Paste the following code at the very top of the file:

<div class="em-event_banner">

<div class="em-event_banner-content">

<h2 class="em-banner_title">Planning an event?</h2>

<p class="em-banner_text">Share your event with our community by using our simple event submission form.</p>

</div>

<div class="submitbutton">

<a class="em-button em-secondary em-big em-event_button" href="https://yourcustomdomain/event/create">

Submit an event

<i class="fas fa-long-arrow-alt-right"></i>

</a>

</div>

<div class="em-event_banner-overlay"></div>

</div>

(4) Save Changes
 

Step 3: CSS

(1) Navigate to Settings > Platform Settings > Appearance > Edit Settings for your Active theme

(2) Click the Custom CSS tab & drop the following code in the box:

.em-event_banner{

margin-bottom: 0;

}

.em-event_banner .em-event_banner-overlay{

border-radius: 0;

}

(4) Save Changes

 

8. Recurring & Past Event Disclaimer

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Shared Among Multiple Views, select the  _event_item file

(3) Add the following code under {% end if %} on line 43:

RECURRING

<div class="recurringmessage">

{% if event_item.has_many_future_instances %}

<p>More dates & times available</p>

{% endif %}

</div>
PAST

{% if event_item.is_past %}{% unless event_item.has_many_future_instances %}

<div class="pastevent">

This is a past event.

</div>

{% endunless %}

{% endif %}

(4) Save Changes

 

9. Link to a Pre-Filtered View of a Group/Department’s Events

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Groups, select Page Shell

(3) Drop the following code on line 45 (between {% endunless %} and </div>):

<a href="{{ group.calendar_url }}/upcoming?order=date&experience=&event_types%5B%5D=37404859896212" class="em-link em-load_more">View Dates & Deadlines<i class="fas fa-long-arrow-alt-right"></i></a>

What is underlined,%5B%5D=37404859896212, will depend on the Filter item you choose. 

You can find this by selecting a Filter from the Filter dropdown on the homepage > clicking Apply Filters. On the resulting page, you’ll find the numerical string in the URL. For example: https://localist.com/events/calendar/upcoming?event_types%5B%5D=37404859896212&experience=&order=date.

(4) Save Changes

 

10. Replace Event Card Labels with Date

Instructions


 
(1) Navigate to
Settings > Platform Settings > Appearance > Edit HTML for your Active theme

(2) Under Shared Among Multiple Views, select the  _event_item file

(3) Delete the snippet on lines 14-19:

{% if event_item.conference? %}

{% event_time event_item order:"first_date" %} - {% event_time event_item order:"last_date" %}

{% else %}

{% event_time event_item order:"date,time,end" %}

{% endif %}

(4) If removing all other card labels, delete lines 38-66, and drop the following snippet of code below in its place. If keeping other labels, drop the snippet either above or below the other labels.

<div class="em-list_tags"> 

<a class="em-card_tag"> 

{% if event_item.conference? %} 

{% event_time event_item order:"first_date" %} - {% event_time event_item order:"last_date" %} 

{% else %} 

{% event_time event_item order:"date,time,end" %} 

{% endif %} 

</a> 

</div>

(5) Save Changes

🤷10 Common Questions: Part 5 🤷

Have you ever wondered what questions other customers are asking? Wonder no more! We’ve rounded up some of the most asked questions below.

Missed our other Common Questions? You can check out 1, 2, 3, & 4 here!

Q: How can I access our Staging Environment?

A: As a Platform Admin, here’s how you’ll access your Staging Environment:

  1. Navigate to your Production Admin Dash > Settings > Platform Settings
  2. Click “Access the Platform Sandbox” in the Platform Environments box in the right sidebar
  3. This will redirect you to the Staging front-end and automatically log you in
  4. From here, select the User Menu dropdown > Administration to access the back-end

Q: How can I test feeds?

A: If you need to test feeds, you should add them in your Staging Environment to make sure events import as expected. Here’s how:

  1. Once in Staging, navigate to the Admin Dash > Events > Feeds > + Add Feeds
  2. Give the feed a Name & enter the URL in the Feed URL field
  3. Fill out the rest of the form accordingly > Save Changes

That said, there’s two important things to note: 

  • An import will run shortly after the feed is initially added and you will see the status on the feed list page. 
  • Feeds will only import once in Staging and will not automatically import each night as they do on your Production platform.

If you experience any issues adding feeds we recommend running it through a validator using a service like, https://validator.w3.org/feed/.

Q: What happens if I make edits to a feed event in Localist?

A: Data imported by a feed will always take precedence over content that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further feed updating:

  • Name
  • Description
  • Place

All other details that are brought in via a feed must be changed at the feed source. If it is changed in any way in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

Q: Can you edit/remove fields on the Public Event Submission Form?

A: For the most part, yes! You can use the Theme Editor to change the text/placeholders and move fields around, but you generally can’t change the functionality of the Public Event Submission Form.

You can also restrict who can access certain fields by navigating to the Admin Dash > Settings > Platform Settings. Under Public Event Submission Form, you can select either All Users, Trusted Users, or Hidden for each field.

Q: Is there an alt-text field for photos?

A: Yup! Here’s where you’ll find it:

If you’re adding an event in the Admin and/or Public Form, scroll to the Photo section > click Upload or Choose from Photo Library > you’ll see a Photo Caption field appear below the image, and this is where you’ll add alt-text.

Even though the field is labeled as “Photo Caption”, it functions as alt-text for accessibility purposes.

Q: Can we set different layouts for events?

A: Yes! You can customize event layouts globally (Settings > Platform Settings > Appearance) or on a per-event basis (Admin Edit an Event Form > Customize Layout). 

  • Global Event Layouts: The Global Event Layout Editor allows for a streamlined layout for all Event Detail Pages on your platform. Select as many components as you feel necessary to provide users with the maximum amount of event details. Just like with Channels, you can arrange these components by dragging and dropping them to the desired position on the page.
  • Per-Event Layouts: The Per-Event Layout Editor allows Admins to set a custom layout for any single event regardless of what the Global Layout is set to. This is great for events that may not require certain components or for the addition of more complex components such as custom HTML.

Q: Can we collect a list of attendees from an event?

A: Sure can! Here’s how you’ll download an attendee report from Localist:

  1. Navigate to an events Edit an Event Form in the Admin Dash
  2. Click View Confirmed Tickets (top bar)
  3. On the resulting page, click Export CSV (top right)
  4. You will receive an email with a link to download the CSV within a few minutes

Q: Can you bulk-add users onto the platform?

A: It’s not possible to bulk-add users into Localist, but this isn’t necessary because Permissions have to be manually added. Each user will need to log into the platform (SSO, Local, or Social) and on their first login, an account will be created. If that person needs their Permissions escalated, a Platform Admin will have to edit their user account accordingly. 

Q: Can you set up multiple levels of approval for Event Admins?

A: Yes, Publish Event is an added Event Admin Permission assignment that allows you to choose if folks can add or edit events via the Admin Event Form and publish them directly to the platform, or if their events should go to the Pending Queue for further moderation:

  • Checked: When checked, Event Admins are able to add, edit, approve, and/or reject events without moderation. This option is checked by default.
  • Unchecked: If unchecked, when an Event Admin adds an event, it will go to the Pending Queue for approval. When an Event Admin edits an event, it will be removed from the live platform and placed in Pending for approval.

Q: Can you use the API to integrate the calendar into an app?

A: Yup, this is exactly what our API was built for! The only caveat here is that this will return raw data as per usual with APIs, so you’ll have to build the code to bring the data into your app. For more information, including how to build a call, please see our master documentation here: https://developer.localist.com/doc/api.

📺 5 Signs You Need to Use a Channel 📺

Channels can be thought of as “Topical Homepages” for subsets of events. Below are the most popular use-cases with examples below each.

1. Do you have a group of temporary events?

Example: A month/week/weekend event series, Seasonal events, Holidays

If you have these types of events you can create a Channel based on a Tag or Keyword. Channels allow you to add context using an HTML component and you can easily turn this Channel’s visibility to hidden once the series ends. 

2. Do you have a collection of events under the same umbrella?

Example: Campus/College/Department events, Athletics calendar

A subset of your org might want to collect all of their events on one page. As long as these folks have their own individual landing pages and/or other Classification set up in Localist, then a Channel can curate event lists.

3. Do you have events with evergreen topics of importance?

Example: Academic calendar, Important dates & deadlines, or Sustainability

Do you have existing Classification that would benefit from curated event lists, extra content, and/or layout customizations? You can set up a Channel to pull those events in and showcase them all in one place.

4. Do you have a collection of private events?

Example: Internal faculty & staff calendar

If you want to keep subsets of events private from the general public or students, you can use Visibility options to create a private Channel. Here’s how it’ll work:

  • Events: Set the Visibility to Restricted > Channels so the event will only appear in the Channel and nowhere else on the Calendar.
  • Channel: Set the Channel Visibility to Hidden so you need a direct URL to access the Channel.
  • Share: Send the URL to the Channel to folks who should see those events. A good place to put this URL is in an email to folks, or in a staff intranet

5. Do you have events that reflect a unique brand?

Example: Branded festival, Branded non-profit initiative  

If you have an event series that includes its own unique brand elements such as colors & fonts that differ from the main brand identity, you can use a Channel to isolate those changes. These extra elements can include Featured Carousels, HTML components, flipped displays, website links, and more.

 

📸 7 Tips for Optimizing Photos 📸

While every organization has their own unique photos, here’s some tips to make sure they work for your Localist platform.

Note: The recommendations below are for our Emphasis theme. Want access to Emphasis? Learn more about upgrading here!

1. Size & Format

Accepted Formats: PNG, JPG and GIF

You should aim to source very large, high quality photos and Localist will automatically scale them down. The max supported size is 5000px x 5000px, and using a 2x retina version of your photos will yield the best results when added to the platform.

We recommend that photos be at minimum 940px x 557px to potentially accommodate being included in the Featured Carousel. However, it’s not always about size when it comes to the effectiveness of photos. You’ll want to consider the proportions of a photo—a rectangular image will translate better than a square in Localist.

Pro Tip: If your image is too tightly cropped, you can add some additional blank space to achieve a rectangular image that will look good across the platform. You can accomplish this by creating a custom design with a 940px x 557px ratio using Canva.

Event Listings:

  • Featured: 940px x 557px
  • Small Card: 290px x 200px
  • Medium Card: 450px x 200px
  • Large Card: 478px x 310px

Event, Place, Group/Dept. Pages:

  • Main Display: 478px x 310px (full width card)

2. Easily Recognizable Photos

Having recognizable photos is important because they not only reflect your brand’s personality, they make scanning and easily identifying content even easier for users. For example, if a user comes to the platform looking for a football game, it will be easier for them to recognize those events if they have football inspired photos assigned to them.

3. Avoid Text Heavy Images

You should avoid adding text-heavy photos (like flyers), as there are multiple viewpoints your users will be referencing them from. Instead, we recommend adding supplemental info to the event’s description so 1) users are provided with the full details, not just what could fit on a flyer, 2) the info will be accessible to those using assistive technology and 3) the content will be available for indexing by Localist and search engines.

4. Photo Cropping

You can adjust custom cropping via the Admin Edit an Event form if you click the pencil icon next to the photo > Adjust Cropping. From here, you can set & lock how the photo looks across the board whether it be it in a card, landing page, Featured Carousel, etc.

5. Cover Photos

Cover Photos are a fantastic way to spruce and liven up your homepage or any Channel. Here’s a few things to keep in mind when adding a Cover Photo: 

  • The recommended size is 1600px x 228px or larger
  • The photo should be subtle like a pattern or landscape.
  • You should consider adding an overlay so the page title & Featured Carousel still pop (you can add one in the Components tab of the Colors, Fonts, & CSS interface) if you’re using an image. 

6. Landing Page Photos

For Place photos, we recommend adding an easily recognizable image of the building itself. For Group/Department photos, you should also aim to add an image that users will associate with the org/club/department.

That said, if you do not have a high-quality image that makes sense then we recommend using a logo. Just make sure that the logo is not too tightly cropped so it doesn’t get cut off on the various viewpoints. 

Pro Tip: Don’t have a unique photo? Localist has you covered with the Photo Fallback Chain. Localist will display one of five photo types (Group/DepartmentEvent TypePlaceEvent/Place Fallback or calendar icon) if an admin or user doesn’t upload an image with their event. 

7. Photo Library

Lastly, Localist understands that not everyone will have a high quality, on-brand image on hand. To fill these gaps, you can fill your Photo Library with images that are not only in line with your brand, but images that will help your events pop.

🥊 12 Localist Feature Face-Offs 🥊

Below you’ll find “face-offs” between some of the most popular Localist features!

1. Groups vs. Departments

Group and Department Pages provide users with context around who is hosting your events. Using them will add a directory to your calendar homepage so users can search via a particular Group or Department, or as a quick way to obtain extra information about the host. 

  • When to use Groups: For student organizations, community clubs, etc.
  • When to use Departments: For academic or internal departments.

Group + Platform Admins

2. Tags vs. Keywords

Tags are used to group like-events that don’t warrant an entire unique Filter. Keywords are effectively hidden Tags as they are only used for internal purposes. 

  • When to use Tags: For short-term or ultra-specifically categorized events. For example, a lecture series, Homecoming, NYE Gala, etc.
  • When to use Keywords: For common misspellings or internal curation effortsi.e. marking specific events for a Widget/Channel.

Event Admins

3. Featured vs. Sponsored

Featured Events are events that you would like to give a prime spot on your calendar homepage or Channels in the Featured Carousel. Sponsored Events will have unique styling to make them pop and get a boost in the Trending algorithm 

  • When to use Featured: For important events that are endorsed by your organization.
  • When to use Sponsored: For events that need a softer endorsement from your organization.

Event Admins + Feature/Sponsor designation

4. Digest vs. Bulletin

Bulletin and Digest allow you to send event newsletters from your Localist platform. Bulletins are sent by Admins and have a higher level of layout and content flexibility. Digests are a self-serve way for users to send events to themselves.

  • When to use Bulletin: For official newsletters sent by your organization.
  • When to use Digest: For users to curate a personalized newsletter of their favorite events. 

Bulletin is available to Bulletin + Platform Admins. Digest is publicly available to all users.

5. Conferences vs. Recurring Events

Conferences are a “moment in time” event spanning multiple days in a row and/or include scheduled sessions within the main “conference.” A Recurring Event is any event that happens more than once.

  • When to use Conferences: For a one-time event that requires sessions, an overnight event, or handling tickets and registration as a whole.
  • When to use Recurring: For an ongoing event with the same agenda and location or handling tickets on a per-instance basis.

Event Admins

6. EventReach vs. EventScore

EventReach is a metric to measure the expected “reach,” or audience awareness, of an event. EventScore is Localist’s trending algorithm which looks at dozens of factors to discover the most popular and interesting events.

  • When to use EventReach: For every event—a healthy score for a typical event will fall above 70%.
  • When to use EventScore (Trending): As your default event list. 

Event Admins

7. Photo Library vs. Fallback Chain

The Photo Library enables you to curate a collection of photos for Admins and users to select within the event submission form. The Photo Fallback Chain ensures that an event never shows up on the calendar without a photo.

  • When to use the Photo Library: For any event where you do not have a unique photo on hand. 
  • When to use the Photo Fallback Chain: If a unique photo has not been assigned to an event. 

Platform Admins

8. Bulk Add vs. Feeds

Localist’s Bulk Add feature allows you to build a Excel (.xls) or CSV (.csv) spreadsheet and upload all of the events at once. Feeds are used to either import event content into Localist or export event content from Localist.

  • When to use Bulk Add: If you’re looking to upload a bunch of events at once or bulk-update existing events in Localist. 
  • When to use Feeds: If you want to import/export event content from another system—but keep in mind that data will be limited.

Platform Admins

9. Feeds vs. the API

 Feeds are used to either import event content into Localist or export event content from Localist. The Localist API will return JSON data that your application can use.

  • When to use Feeds: If you want to import/export event content from another system—but keep in mind that data will be limited.
  • When to use the API: If you’re looking to integrate Localist content into another system’s internal interface with JSON data.

Feeds are available to Platform Admins. The API is publicly available to all users.

10. The API vs. Widgets

The Localist API will return JSON data that your application can use. A Widget enables you to create events once in Localist and publish everywhere with a simple embed code. 

  • When to use the API: If you’re looking to integrate Localist content into another system’s internal interface with JSON data.
  • When to use Widgets: If you are only looking to display content on other pages as it’s quicker and generates styled data.

Both the API and Widget Builder are publicly available to users. 

11. Widgets vs. Channels

A Widget enables you to create events once in Localist and publish everywhere with a simple embed code. Channels are a promotion tool that pulls your events based on already existing Classifications (or date ranges) to showcase them in one place.

  • When to use Widgets: If you’re looking to display Localist events on your website’s homepage, a department landing page, or community partner’s website.
  • When to use Channels: If you’re looking to create a dedicated “homepage” to a specific collection of events within Localist. 

Channels are available to Channel + Platform Admins. The Widget Builder is publicly available. 

12. SSO vs. Local accounts

Single Sign On (SSO) enables users to login and create an account using the credentials they use for your organization. Local accounts are created directly through Localist.

  • When to use SSO: If your organization uses SSO for account management.
  • When to use Local: Unless you’re using LDAP SSO, you can always have Local logins available so people outside your organization can create accounts. 

Platform Admins

🖍 How to Categorize Your Events Like a Pro 🖍

Whether you’re new to Localist or already a seasoned admin, this guide will help you find the best home for every category and label your community needs to browse and manage events effectively. 

When to Use Landing Pages

Does it reflect a location? → Place

Example: Concert Hall

Adding locations as Filters will clutter your list and is a misuse of a Localist feature. Localist provides Place Pages for this exact purpose! Places give you the ability to create a directory for users to browse, increase SEO by adding more pages to your site, and provide additional context surrounding the location of your events.

Does it reflect an organization? → Groups or Departments

Example: Book club, Office of Student Affairs

Similar to Places, Localist provides Group and Department Pages that can be used to house any common event hosts, groups, organizations, departments, associations, clubs, etc. If there is a common host, then Groups and Departments are your solution!

When to Use a Tag or Keyword

Will it be used for a temporary time period?

Example: Festival, Homecoming, Halloween, or Black History Month

If a Filter is not used year-round, then it should be a Tag. These are only serving your users for a small percentage of the year, while inhibiting their browsing experience for the majority of the year.

Does it communicate internal details?

Example: Homepage widget, special event

If you have Filters that are mainly used for internal curation efforts, then they should be Keywords instead. For context, Keywords are essentially hidden Tags and they’re mainly used internally for SEO, common misspellings, and Widget/Channel filtering.

When to Use Filters

Does it communicate the format of an event? → Event Type

Example: ​​Concert, Workshop, Auction

This Filter Family provides context surrounding the format of an event and communicates what an attendee will be doing or experiencing at the event.

Does it communicate who the event is for? → Target Audience

Example: General Public, Family-Friendly, LGBTQ+

This Filter Family provides context surrounding who can attend an event.

Does it communicate a mission or strategic goal? → Topic

Example:  Arts & Culture, Health & Wellness, Sustainability

This Filter Family provides context surrounding the information covered, overarching goals, initiatives or themes surrounding or influencing an event. 

Additional Filter Streamlining

Review for duplicates/overlapping

Example: Alumni (Event Type), Alumni (Target Audience)

If your Filter list has duplicates, you run a high risk of admins and users only selecting one or none at all when adding events. 

Remove “Yes/No” Setup

Example: Open to the Public > Yes, No

Filters should never be formatted as a question/answer. In instances like these, the absence of “Open to the Public” and the presence of another Target Audience Filter like Students, Alumni, Faculty & Staff, etc. will be clear enough.

Remove Filters with one child

Example: Lectures > Presentations OR Music > Concerts

Child Filters should only be used when absolutely necessary. By their very nature, Child Filters run a high risk of being too granular and not contributing to a positive user experience. 

👍 10 “Rules of Thumb” for Your Calendar 👍

Have you ever wondered how much of each feature other customers are using? Wonder no more! We’ve rounded up some of our top “rules of thumb” to help you gauge how much is too much!

1. How many admins should we have?

Rule of thumb: The average customer has around 15 admins.

Best practice: We recommend at least having a handful of Admins with no restrictions so they have full access to everything in the Admin Dash.

2. How many brand customizations do we need to make to the calendar?

Rule of thumb: Fonts, colors, and a logo

Best practice: Whether or not you keep it simple or include a full header/footer depends on your online brand identity and technical resources. At the end of the day, your events will be your “brand”.

3. How many login options should we use?

Rule of thumb: At least 2

Best practice: We recommend using all available options—Local, Social and if available, Single Sign-On— to ensure the broadest community is able to access features that require accounts, such as “I’m Interested.”

4. How many Bulletins should we send?

Rule of thumb: At least once a month

Best practice: Ultimately, how often you send a Bulletin will depend on the number of events you are hosting on a rolling basis and how often new events are scheduled.

5. How many Widgets should we have?

Rule of thumb: At the absolute minimum, at least one on your website’s homepage

Best practice: We recommend creating Widgets for all landing pages that align with your Classification (Filters, Groups, Departments, and Places).

6. How many Filters, Groups & Departments, and Places should we have?

Rule of thumb: At most 7 Filters per set, but no limit for Groups & Departments and Places.

Best practice: While we always recommend keeping these lists on the smaller side for easy browsing, you can technically include as many as you’d like as long as they’re relevant, used often and easily understood by your community.

7. How many Channels should we have?

Rule of thumb: No limit

Best practice: They should not be a mirror of your homepage or Classifications. A Channel should be creating a unique, additional layer to your event content to highlight a specific subset of events.

8. How many photos should we have in the Photo Library?

Rule of thumb: 12

Best practice: You can technically include as many photos as you’d like as long as they’re relevant, used often, and easily identified by your community.

9. How many Sponsored Events should we have?

Rule of thumb: No more than ½ the amount of events displayed in the Event List

Best practice: We understand that there’s always a need to Sponsor specific events, but you should also aim to have a mix of organic trending events on your homepage.

10. How many Feeds should we have?

Rule of thumb: No limit

Best practice: Aim to centralize as many event efforts as possible by adding events directly to Localist first then promoting them on external pages via Widgets, an event Feed or our API.

Localist Admin Group

The Localist Admin Group, powered by LinkedIn, is a peer space to connect, swap tips, share solutions and provide insights with other Localist Administrators.

📍 4 Ways to Use Widgets on Your Website 📍

Widgets allow you to create events in Localist and seamlessly publish them anywhere on the web. Below we’ve outlined some ways you can incorporate Widgets of every shape & size into your websites:

Widgets as Supporting Content

1. Prominent

A prominent Widget communicates to your audience that events are very important to the organization. If you’re trying to grab folks’ attention and drive traffic back to the calendar, we recommend a Widget with eye-catching photos that takes up a substantial portion of a page.

Where?

  • On your website’s homepage
  • On a departmental website’s homepage
  • On a community partner’s homepage
  • In a community newsletter
  • In digital signage (TVs, digital billboards, video walls)

 

Customer Example: University of North Dakota → John D. Odegard School of Aerospace Sciences

2. Complimentary

A complimentary Widget may still have its own dedicated section and have images but it’s typically a bit more flexible in terms of placement. This size Widget is perfect to pair alongside other valuable content to help increase event exposure within your community.

Where?

  • Within a news & events section of your homepage 
  • A section of a departmental homepage/landing page
  • A section of a community partner’s homepage/landing page
  • Within a news article or blog post

 

Customer Example: Florida State University → Office of Financial Aid

 

3. Supplemental

By comparison, a supplemental Widget is typically pretty small, and as such, you can sneak them into any corner of a website to help promote events to a wide audience.

Where?

  • In your website’s footer
  • Within the sidebar of various landing pages on your website, departmental websites, or community partner’s websites

 

Customer Example: MIT → Center for International Studies

Widgets as the Main Content

4. Full Page

These Widgets should be the main content of an entire page. Think of it like this: If not for the Widget, the page would not exist because its sole purpose is to provide event content.

Where?

  • On a landing page dedicated to events

 

Customer Example: University of Southern California → Rossier School of Education