Email Templates allow you to customize the HTML of the email notifications sent by your platform. The template language is Liquid. This tool does not include Bulletin newsletters. Learn more about customizing Bulletins here.
Start by navigating to Settings > Platform Settings > Appearance and select Edit HTML for your Email Templates:
By default, all emails will include your organization’s name in the header as it is set in the Platform Display Name field via Settings > Platform Settings:
To display a logo instead of your Platform Display Name, upload a logo in the below Logo & Link field:
To change the Font Colors and Font Families being used across all email notifications, open the template _header found under Shared. You’ll find the following on lines 7-23:
To further edit the content of the email notifications, you will need to edit each notification individually:
| Template | Details |
|---|---|
| Tomorrow’s Plans | When a user marks themselves as “I’m Interested,” an email will send the day before the event occurs to remind them that they have plans the next day. If the user is interested in more than one event, it will show them a full list, not sending one event per email. |
| Template | Details |
|---|---|
| Digest | Allows Users to curate their own event campaigns. Digest are customizable to suit your interests, and are a great way to stay informed and engaged in your community without having to proactively visit the site. |
| _component_spacer | Controls the space between components in Digests. |
| Template | Details |
|---|---|
| Feedback Request | Event Insights is a flexible survey that is sent to users after an event to help you understand how each event contributes to your community goals. This survey helps you gain deeper insight from event attendees about the topic, format, and overall experience of your events to better inform your community event engagement strategy. |
| _styles | CSS stylesheet for Event Insight emails. |
| Template | Details |
|---|---|
| Notification Email Shell | The outer shell for all notification emails. |
| Event Changed | Edit the content and language included when a change to your event has been made. |
| Event Invitation Accepted | Sent when an event you send to another User is accepted. |
| Event Invitation Received | Sent when an event invitation you send to another User has been received. |
| Event Invitation Rejected | Sent when an event invitation you send to another User has been rejected. |
| Event Rejected | Email notification sent to a User when their submitted event has been rejected by an Event Admin. |
| Event Submitted | Notification email confirming your event has been submitted via the Public Submission Form. |
| Event Verified | If an Event Admin accepts and publishes your submitted event. |
| Friend Request Accepted | If you send a friend request to another User and they accept. |
| Friend Request Received | If you sent a friend request to another User and they have received it. |
| Group Membership Approved | If following Groups or Departments requires moderation on your platform, and a Group Admin or Group Officer approves it. |
| Group Membership Requested | If following Groups or Departments requires moderations on your platform, and you’re a Group Admin or Group Officer managing the following list. |
| Message Received | When you send a message to a friend in Localist and they receive it. |
| Reset Password | Request a password change in Localist. Note that this only works with Local logins. If you need to change your SSO credentials you must go through your organization’s IT team as Localist does not manage SSO passwords. |
| Site Invitation | Invitation to join your organization’s Localist community platform. |
| Verify Account | After signing up for a Localist account, verify your email to ensure you were the one to create an account with your email. |
| Template | Details |
|---|---|
| In-Person Ticket | Localist Register tickets that are flagged as in-person. |
| In-Person Ticket PDF Attachment | PDF thats included in your Localist Register in-person ticket email |
| New Ticket Purchase | Sent to the owner of an event after a User purchases a Localist Register ticket. |
| Order Receipt | Receipt for the Localist Register ticket you purchased. |
| Order Refunded | Sent if your Localist Register ticket is refunded. |
| Ticket Refunded | ?? |
| Ticket Voided | If your Localist Register ticket has been voided. |
| Virtual Ticket | Localist Register tickets that are flagged as Virtual. |
| Wait List Ticket | Localist Register tickets that are flagged as Wait List. |
| _footer | Localist Register email footer area. |
| _header | Localist Register email header area. |
| Template | Details |
|---|---|
| _footer | Controls the footer for all notification emails. |
| _header | Controls the header for all notification emails |
In this area of the Admin Dash, you’re able to 1) set your platform’s login options 2) add your organization’s social media URLs and 3) integrate with third-party software to automate tasks, improve reporting, and enhance your audience’s experience. Navigate to Admin Dash > Settings > Apps & Integrations
If the code you’re seeing is UA-38181101-1, this belongs to Localist and cannot be removed at this time. If this is not the UA code in question, double check 1) the UA code on your Apps & Integrations page, and/or 2) the <head> of your platform via Theme Editor > Global Site Shell for any discrepancies.
Sure can! To add yours, navigate to your instance of Google Tag Manager and copy the GTM embed code snippet. From there, navigate to your platform’s Theme Editor > Wrapper > Global Site Shell and paste your embed code as close to the opening <head> as possible before saving changes. That being said, if you are using a SILK Wrapper, you will need to add GTM directly to your SILK Wrapper file and refresh it.
| Field | Details |
|---|---|
|
|
|
|
|
|
|
|
|
| Field | Details |
|---|---|
| RSS | Enter the URL for an RSS feed you’d like to integrate with on the platform – i.e. a news feed. |
| Zoom | Check this box if you wish to turn on the Zoom Integration for your platform. |
| Salesforce | Connect with Salesforce to automatically export your event’s attendee data to your Salesforce account. |
| Cvent | Automatically import your organization’s Cvent events |
| Concept3D | Replace the standard Google Maps with your Concept3D maps on Place and Event landing pages. |
| HubSpot | Automatically export your event’s ticket purchase/registration data to your HubSpot account. |
Fetch any content in Localist, to be used in your own apps. To get started click + Add App
| Field | Details |
|---|---|
| Name | Give your app a recognizable name |
| App Website | Enter the URL for your App |
Once your app has been created, you can add Access Tokens for your app to access the Localist API by clicking Manage Access Tokens. On the resulting page, create an access token and fill in the following fields:
| Field | Details |
|---|---|
| User (required) | Type an existing user’s name, or email address |
| Expires | Set a date for the user’s access expiration |
| Access | Your options are:
|
Your Brand Template will be the header & footer of your calendar! You’ll need to identify a page with the header & footer you’d like to use and then just follow the steps below.
</header> and before <footer>
</header> locate this content and leave it intact<meta> content<base href=””> and/or ”canonical”<head> content <head> content into Global Site Shell on the line just before the <!-- begin include javascripts --> comment > Save Changes<header> content (beginning with the <body> tag) and paste it into the _header file on the line before the {% if site.show_navigation %} statement > Save Changes <a class="em-desktop-menu-title" href="{{ site.home_link }}">
{% if site.has_logo %}
<img src="{{ site.emphasis_logo_url }}" alt="{{ site.name }}" height="{{ site.emphasis_logo_height }}" width="{{ site.emphasis_logo_width }}" {{ site.emphasis_logo_srcset }}>
{% else %}
{{ site.name }}
{% endif %}
</a>
<footer>content <footer> content into _footer on the line before <div class="em-subfooter"> > Save ChangesOnce you’ve completed these steps, navigate to Admin Dash > Settings > Appearance > click on the paint brush icon for your Active Theme to begin corrective CSS + adding colors, fonts, etc.
You can use Localist’s Theme Editor to access your platform’s HTML to customize how your event data is presented. The template language is Liquid.
On the +Add Theme page you will be prompted to enter a name for the theme, and which existing theme the new theme will inherit.
| Field | Details |
|---|---|
| Activate | This will tell Localist to make the theme you’re editing live, replacing the previously active theme. |
| Delete | This will remove the entire theme. |
– HEADS UP –
When new features and upgrades are made available, you can now easily and quickly review the necessary template changes in our public template repository. As a reminder, your platform will be automatically updated with these changes if no customizations have been made to the corresponding template. However, if you’ve edited a template, you will need to apply these updates manually. For access to our template repository, please submit an access request:
When modifying a file, in order for your changes to stick you must Save Changes before you navigate to another file. If you select another file before saving your changes, you will receive a warning prompt that the file contains unsaved changes. After saving a file, it will be blue bold in the file list.
If you are using a SILK Wrapper, then changes made to the Global Site Shell file will not be applied. After you have saved your changes in a file, a Reset to Default link will appear next to the Save Changes button. Selecting this will remove all changes you’ve made to the specific file.
| Partial | Details |
|---|---|
| README | This is an internal file available for you to document any common changes, or things to keep in mind for your staff as you customize your platform. |
| Public Help Page | This is an open HTML page for you to provide a page of guidelines, instructions or an FAQ for your users. |
| Partial | Details |
|---|---|
| Channel Page Shell | The base shell for all Channels. |
| Add Events Block Component | The default Share Events and Widget Builder box. |
| App Store Buttons Component | Allows you to link directly to any apps you have in the App Store. |
| Channel List Component | A list of some or all of the Channels on your platform. You are able to select which ones you want to appear. |
| Community List Component | A list of the Communities on your platform. |
| Department List Component | A list of the Department Pages on your platform (with links). |
| Description Component | A description box to add to your Channel. |
| Event List Component | A list of events (each list will have its own label to toggle between lists). |
| Event Spotlight Component | Showcase a specific event. |
| Event and Featured Tabs Component | Each section where the event list or Featured Events Carousel appears. |
| Featured Section Component | Add a Featured Events Carousel(s) to your Channel. |
| Filter List Component | Your platform’s Filter list (you cannot have a Channel specific filter list). |
| Google Map Component | A map of all your events in the Channels with pins at each event location with a list of events happening there. |
| Group List Component | A list of the Group Pages on your platform (with links). |
| HTML Component | Any HTML embed you would like (i.e. a weather bot for a festival). |
| Header Component | The header section of a Channel. |
| Hero Image Component | An image that can link to a website (great for advertisements). |
| Mini Calendar Component | The navigational mini calendar. |
| Place List Component | A list of the Place Pages on your platform (with links). |
| Platform Navigation Component | The navigation buttons to help your users find events (All Events, Places to Go, Groups, Departments). |
| RSS Feed Component | Add an RSS news feed. |
| Social Links Component | Add a Facebook, Twitter, and/or Instagram button linking to your respective account(s). |
| Submit Event Button Component | Takes users to the Public Event Submission Form. |
| Website Link Component | Add a link to an external website, like a festival page or registration form |
| Partial | Details |
|---|---|
| Page Shell | The base shell for all Event Pages: Name, photo, time, dates + instances, place, filters, tags, website, cost, groups, departments, hashtag, custom fields, subscribe links, recent activity (comments, photos, reviews), event owner edit, admin edit. |
| Invite Friends | The lightbox content and messaging that is displayed when a user selects the Invite Friends button. |
| Public Event Submission Form | Name, description, schedule (start date, start time, end time, repeating, summary), location (place, room, address), additional details (hashtag, website, custom fields), photo, filters, departments, groups, ticketing (cost, link). |
| User Multi-Date Select | The lightbox content and messaging that is displayed when a user selects the I’m Interested button on events that have multiple instances. |
| _edit_sidebar | The right sidebar of the Public Event Submission Form. Includes “Adding an Event” and “Batch Event Add” boxes. Often used for custom guidelines, disclaimers and organization specific tips. |
| _event_attendees | The People Interested box on Event Pages. |
| _event_buttons | Buy Tickets/Register, Invite Friends and I’m Interested buttons on Event Pages. |
| _event_status | A user’s “I’m Interested” status and functionality on Event Pages. |
| _right_sidebar | The right sidebar for all Event Pages: Getting Here (map) box, event directions and all other “Event” partials. |
| _share_links | AddThis social sharing options displayed on the left side of the browser on all Event Pages. |
| Partial | Details |
|---|---|
| Page Shell | The base shell for all Group (and Department) Pages: Metadata, photo, name, website, description, filters, custom fields, upcoming events, recent events, Group feed, recent activity, follow group, followers. |
| _group_buttons | Follow Group, Twitter, Facebook. |
| _group_members | Followers box on all Group (and Department) Pages. |
| _group_request_form | The lightbox and messaging for when a Group requires approval to follow. |
| Partial | Details |
|---|---|
| _add_event_block | The default Share Events and Widget Builder box in the right sidebar. |
| Partial | Details |
|---|---|
| Page Shell | The base shell for all Users’ messaging center. |
| User Contact Form | Admin contact form for users. Also includes right sidebar guidelines for contacting Admins. |
| _compose_form | Compose a message to friends page. |
| _conversation | View conversation with a friend: select a message, view previous conversations. |
| _conversation_list_item | View conversations within a list: delete conversation. |
| Partial | Details |
|---|---|
| _edit_text | Group description editor (only appears for Group Officers). Allows Group Officers to edit the description text of their Group without having access to the Admin Dash. |
| _login | The login lightbox including content from _login_message and _login_methods. |
| _login_message | Includes lightbox description copy: “Login to interact with events, personalize your calendar, and get recommendations.” |
| _login_methods | Includes all available login option buttons. |
| _ticket_lightbox | Pop up lightbox that is displayed when a User clicks “I’m Interested,” but the event has an external registration link (i.e. a “you still need to register!” reminder). |
| Partial | Details |
|---|---|
| Page Shell | Landing page for a user’s photos available via “Photos” in the User Menu. |
| _album_contents | List of user uploaded photos available via “Photos” in the User Menu. |
| _edit_photo | Includes caption, photo location, related events and ability to make a photo a user’s default. |
| _no_photo | “Click on a photo” box in the right side column on the “Photos” dashboard. |
| Partial | Details |
|---|---|
| Place Page Shell | The base shell for all Place Pages: Metadata, photo, name, website, description, filters, custom fields, upcoming events, recent events, recent activity, follow place, followers. |
| _business_buttons | Follow Place, Twitter, Facebook. |
| _share_links | AddThis social sharing options displayed on the left side of the browser. |
| Partial | Details |
|---|---|
| Registrant Text Page | This is where you’ll edit subscription ‘terms’ text. |
| Partial | Details |
|---|---|
| Page Shell | Landing page for a user’s reviews available via “Reviews” in the User Menu. |
| _manage_reviews_list | Includes a list of events needing review and previously posted reviews. |
| _review_form | The form for submitting a review of an event including these options: “I didn’t like it,” “Meh” and “It was great!” |
| Partial | Details |
|---|---|
| Search Results Page Shell | The initial landing page displayed after completing a search. This page is available at /search. |
| User & Place Calendar Page Shell | The page resulting from selecting “view full calendar” from a User Profile or Place Page. |
| _calendar_filter | Similar to browse_filter. It’s the filter list that appears on the side of Place/User calendars. |
| _event_list | Event listings on all pages starting with /calendar. |
| _minicalendar | The navigational mini calendar on Search Results pages. |
| _result_block | The initial landing page for all search results. |
| _right_side | The right sidebar for all search results. |
| _subscribe | Google Cal, iCal, Outlook and RSS subscription links on search and filtered results pages. |
| Partial | Details |
|---|---|
| _activity_photo | The photo section of Event, Place, Group and Department pages. |
| _browse_filter | Filter and Community lists on all pages except Channels (including Homepage). |
| _comment | The comment section of Event, Place, Group and Department pages.> |
| _comment_form | The form used for commenting directly on Event, Place, Group and Department pages. |
| _event_item | All Event listings on your Localist platform: Name, Event Type Filters, description, start date, start time, Place, photo, I’m Interested, Register/Buy Tickets CTA. |
| _featured_section | All Featured Event carousels on your Localist platform: Name, photo, description, start date and start time. |
| _flash_message | The alert bar that appears near the top whenever something is saved, a form submission error, etc. |
| _minicalendar | The Mini Calendar on all pages except Channels (including Homepage). |
| _nav_after | The space before the platform nav section (Submit, All Events, Groups, Departments, Places to Go). |
| _nav_before | The space after the platform nav section (Submit, All Events, Groups, Departments, Places to Go). |
| _next_page_link | The pagination containers that include back and next arrows when viewing event’s by Day, Week or Month. |
| _platform_nav | Includes Submit an Event, All Events, Groups, Departments and Places to Go buttons. |
| _recent_activity | This is the interface for Comments, Reviews and Photos included on Event, Group, Department and Place pages. |
| _review | The review section of Event, Place, Group and Department pages. |
| _review_form | The form for submitting a review of an event including these options: “I didn’t like it,” “Meh” and “It was great!” |
| _upload_photo_form | Photo upload functionality included in the Recent Activity section on Event, Group, Department and Place pages. |
| Partial | Details |
|---|---|
| Password Forgot Form | Landing page for starting the password reset process for a local account. This page is available at /auth/forgot. |
| Password Reset Form | Landing page for setting a new password for a local account. |
| User Account Verification | Users are taken to this page after their email address has been verified. |
| User Login | The non-lightbox login page. Viewable at http://calendar.url/auth/login. By default, it includes the files from the login lightbox on a static page. |
| User Signup | Landing page for creating a new account. This page is available at /signup. |
| Partial | Details |
|---|---|
| Dashboard Shell | The base shell for all user dashboards available via User Menu > Dashboard: Welcome message, user’s upcoming events, Widget CTA, Platform Nav and Profile Completeness. |
| Public User Page Shell | The base shell for all user profiles available via User Menu > Public Profile: name, photo, upcoming events, recent activity, places followed and friends. |
| Add Digest | The form used to initially create a new Digest. |
| Bulletin Settings | In the User Menu > Settings > Bulletin tab, this shows a list of all Bulletins the User is subscribed to. |
| Calendar Digests | The Digest management page available via Settings > Digest in the User Menu. |
| Digest- _example_widget | In the Digest form (right sidebar), this is a simple description of a Digest. |
| Digest- _form | The Digest Email builder form available at /digester/summaries/new. |
| Digest Edit | The form used to edit a current Digest. |
| Edit Profile | The base shell for the user settings page available via User Menu > Settings: account settings, notifications, Bulletins and privacy. |
| Manage Friends & Places | Landing page for a user’s Friends & Places available via “Friends & Places” in the User Menu. |
| Manage Groups | Landing page for a User managing the Groups they “follow” available via “Following” in the User Menu. |
| Notification Settings | Interface where users can customize their notification settings available via Settings > Notifications in the User Menu. |
| Privacy Settings | Interface where users can customize their privacy settings available via Settings > Privacy in the User Menu. |
| _feed_item | The individual items in the list of updates and notifications in a User’s Dashboard. |
| _feed_list | The list of updates and notifications in a User’s Dashboard. |
| _friends_tab_block | The “following” page in a User’s Dashboard. |
| _pending_event | A list of pending events in the User’s Dashboard. |
| _request_item | A catch all of notifications a User will get if someone wants to follow them. |
| _user_buttons | User notifications like sending a message or confirming a follow. |
| Partial | Details |
|---|---|
| Widget Builder Form | Landing page for building Localist Widgets. This page is available at /help/widget. |
| _examplewidget | Includes “Put Events on Your Site” and “Widget Help” boxes in the right sidebar of the Widget Builder page. |
| _feed_event | When using the Widget Builder to generate an RSS feed, this is the file it will use. Allows the admin to change the output of RSS for all RSS widgets on the platform (or they can make a new widget). |
| Partial | Details |
|---|---|
| Global Site Shell | Base shell for all Localist pages. Includes <head> elements and can be used to embed scripts. This file is disable when using a SILK Wrapper. |
| _footer | Localist added footer. Includes “powered by Localist” messaging. This file is disabled when using a SILK Wrapper. |
| _header | Localist added header. Includes logo, user menu and Localist search bar. This file is disable when using a SILK Wrapper. |
| _search_bar | Localist specific search bar. When using a SILK Wrapper this is added to your platform with an HTML comment. |
| _user_menu | Localist specific user menu. When using a SILK Wrapper this is added to your platform with an HTML comment. |
Events are available in two formats:
| Format | Details |
|---|---|
| Listing | event_item
|
| Landing Page | event
|
| Property | Details |
|---|---|
.name |
Full title of the event |
.url |
URL to the event’s unique landing page |
.description_text |
Plaintext event description |
.description |
Full HTML event description |
.place |
Name of the event’s location |
.venue |
Name of the Place Page connected to the event |
.ical_url |
ICS subscription link for the event |
.photo |
The photo assigned to the event |
.tags |
All Localist Tags included with the event |
.keywords |
All Localist Keywords included with the event |
.website |
The external Event Website included with the event |
| Property | Details |
|---|---|
.starts_at |
Full start date and start time |
.ends_at |
Full end date and end time |
.start_date |
Date the event starts |
.start_time |
Time the event starts |
.end_time |
Time the event ends |
.first_date |
Date of the earliest instance of a recurring event |
.last_date |
Last date of the latest instance of a recurring event |
.next_instance |
Next upcoming instance of a recurring event |
.future_instances |
Next 8 instances of a recurring event |
.created_at |
Timestamp of the event’s creation |
.updated_at |
Timestamp of the event’s last update |
| Property | Details |
|---|---|
.is_sponsored |
The event has been marked as Sponsored |
.is_over |
The event’s end time has passed |
.is_past |
The event’s start date > today |
.has_many_future_instances |
The event has recurring future instances |
.is_verified |
The event has been approved and is live |
.is_rejected |
The event has been rejected and is not live |
.allows_attendance |
Users can use the “I’m Interested” functionality for the event |
.has_instances |
The event is a recurring event with multiple instances |
.has_tickets |
Localist Tickets are required for one or more instances of the event |
.needs_registration |
Localist Registration is required for one or more instances of the event |
.has_external_tickets |
An external ticket/registration URL is included with the event |
Language Changes refer to any time the default language on the platform is changed to display a different word or phrase. The majority of languages are made by the customer using the Theme Editor to modify the platform’s HTML. However, there are some pieces that need to be changed on Localist’s end. Localist Language Changes include:
The files noted are found in the HTML Theme Editor by navigating to Settings >Platform Settings > Appearance > Select Edit HTML for the appropriate theme.
Localist Platform Homepage
Share Events Box: Homepage > _add_event_block
Public Event Submission Form
Adding an Event + Batch Event Add Boxes: Events > Public Event Submission Form
Landing Pages
Getting Here map header:
Recent Activity Section (header, comment, review, photo and no recent activity): Shared Among Multiple Views > _recent_activity
Upcoming Events header, Recent Event header & “View full calendar” link:
In this area of the Admin Dash, you will find 1) general platform-wide settings and 2) appearance settings (CSS and HTML).
Navigate to Settings > Platform Settings.
| Field | Details |
|---|---|
| Platform Display Name | This is the name that is displayed in breadcrumb links, feed data, emails and notifications for the platform. |
| Physical Address | This will be used in the footer of all notification emails to prevent messages from being directed to spam folders. |
| Contact Email | This can be any one email address. There is a Contact Us link on the event submission form and all inquiries from that form will be sent to this address. |
| Pending Digest Email | This can be any number of emails. Every day at 4 PM a pending digest that includes a list of events in the pending queue will be sent to the specified emails. The digest does not take into account any filter restrictions on a user’s account, but when they navigate to the pending queue they will only see events that correspond to their restrictions. |
| Platform Time Zone | Select one that applies. |
| Silent Mode | When checked, Localist will not send any emails/notifications to users.This is unchecked by default. |
| Allow Community Event Posts | When unchecked, the “submit an event” button will be removed from your calendar homepage and events will only be able to be added by administrators in the admin dashboard. Audience event submissions are allowed by default. |
| Moderation Level | Applies to all event comments.
|
| Field | Details |
|---|---|
| SILK Wrapper (Brand Template) URL | If you are using our SILK Wrapper feature, save your wrapper’s URL here. To activate the new wrapper or force an update, select the Refresh Wrapper link below the field. |
| Include Localist Styles | Unchecking this setting will remove all default CSS from the platform. |
| User Help URL | This URL will be posted on your platform’s Admin Dash. |
| Default Date Range | Dictates the time range and amount of events that will be displayed upon selecting a filter so the number on the homepage will always reflect this. Select one of the following:
|
| Show Event Types on Event Items | If checked, the Event Type associated with events will display when events are in lists (i.e. Trending, all events, Filtered pages, etc). |
| Default Map View | Select one of the following:
|
| Logo & Link | If you are not using a wrapper or header/footer template, you can upload a logo here that will display in the top left corner of the default header. The URL entered will be attached to the logo. |
To edit the CSS of the Default or custom theme, select Edit Settings. To add a custom theme, please refer to our Theme Editor documentation. On the theme’s settings page, you will find the following:
| Field | Details |
|---|---|
| Variants | Out of the box, Localist offers four variants that can be used as the base of your theme:
|
| Global Elements | Here you’ll find:
|
| Components | This is where you can adjust the grid column widths. |
| Custom CSS | This is where you enter and save Custom CSS to target individual elements. |
Localist’s custom domain feature is an essential component of your overall brand identity being applied to your platform as it changes the display of your Localist URL to a subdomain of your current website. Once you have your Custom Domain in place, you’ll need to get SSL setup for the most secure browsing experience.
SSL is now self-serve right in the Admin Dashboard, so you no longer have to contact the Localist support team for assistance! You can request a CSR, upload your certificate and secure your Localist platform in one convenient location.
When it’s time to update, you’ll just have to navigate to the Settings > Platform Settings > Domain & Security.
Localist is not your certificate authority as we do not provide nor manage your Custom Domain. While we can’t say for sure who each customer’s certificate authority is, in our experience, it’s the same third-party that is providing your domain. Your best bet here is to reach out to your IT team, or the folks that manage your website, to see if they have more information here.
Your calendar’s custom domain is set up by using a CNAME record. Your custom domain will need to be a subdomain to your website, such as events.yourwebsite.com, and not set as a subdirectory, such as yourwebsite.com/events.
Once your custom domain secured through your domain registrar, follow these two steps:
– HEADS UP –
It can take 24-72 hours for domain settings to propagate across the world. Confirm the domain has fully propagated before taking this step. You can confirm it through websites like https://dnschecker.org/.
Navigate to Settings > Platform Settings > Domain & Security.
| Field | Details |
|---|---|
| Force HTTPS | All connections requested over http will be automatically redirected to HTTPS sessions. This redirect will occur for every HTTP request. |
| Stricter Transport Security | Similar to “Force HTTPS,” the STS policy, tells a browser to never use HTTP. However, once the first redirect occurs, the user’s browser will never attempt an HTTP connection and will instead go directly to an HTTPS session. Once set, this setting cannot be undone as individual user’s browsers will retain the STS header setting even if turned off by the customer. |
| Content Security Policy | When turned on, this setting blocks JavaScript from third party domains. This should not be turned on if you are using our SILK Wrapper feature or you have added your website’s header/footer template to the HTML Theme Editor.
|
| Referrer Policy | Tells the browser to include the URL of the page a user is initially on when navigating to another page. Turned on by default. |
| Feature Policy | Turns off computer microphone and camera access, except for those platform’s using Localist Register’s Organizer Check-In scanning for QR codes. Turned on by default. |
Navigate to Settings > Platform Settings > Domain & Security > + Generate CSR. Fill out the following (fields marked with * are required):
| Field | Details |
|---|---|
| Custom Domain | Enter your platform’s Custom Domain. |
| Country (C)* | Enter your two character country code. Ex: US. |
| State or Province (ST)* | Enter your state. Do not abbreviate. |
| City or Locality (L)* | Enter your city. Do not abbreviate. |
| Organization (O)* | Enter your org’s official name. |
| Organization Unit (OU) | Usually used for something like a Department name. This field is optional. |
RSA Key Size: select either 2048 bit OR 4096 bit.
Once complete, click the Generate CSR button. From here, you’ll need to submit the CSR to your certificate authority. We will need the certificate and intermediates sent back in format X.509, PEM encoded. For some systems, that can be listed as “Apache2 + mod_ssl/ .pem” or “X.509 Certificate Only, Base64 encoded” and “X.509 Intermediates/root only Reverse, Base64 encoded“.
Once you have the SSL cert from your certificate authority, navigate to Settings > Platform Settings > Domain & Security > + Upload Certificate. Upload the following:
– HEADS UP –
The certificate and private key must be in X.509 PEM format, without a password. You’ll need to upload both the Certificate File and Private Key (if this is the first time you’re setting up SSL on your platform).
Intermediate and Root certificates are not required.Localist’s configuration utilizes a database of intermediates and automatically uses the appropriate one based on the certificate that’s been uploaded.
After your certificate is uploaded, you will see it added as an entry to the certificate log on the main Domain & Security tab. 30 days before the certificate expires, the platform’s main contact will receive an email alerting them of the upcoming expiration.
When it comes time to update your certificate, start by following the previously outlined steps for generating a CSR. Again, you will submit this to your certificate authority to obtain a new certificate. Once obtained, select the linked domain name to update your new certificate. From here you will upload your certificate, no private key required.
Localist offers three branding tools (Brand Template, Custom CSS, and the HTML Theme Editor) that work together to achieve anything from a basic theming to extensive customization.
As your main branding tool, the Brand Template allows your Localist platform to adopt your main website’s header, footer, and base CSS. For organizations looking to achieve a slick, but simple level of customization, implementing a wrapper is the first and only step toward achieving 100% brand adoption.
Custom CSS allows you to make surface level changes to elements that are already built, whether by the customer or provided out-of-the-box by Localist. You can add Custom CSS to the stylesheet within your wrapper or directly into Localist. With Custom CSS, you’re able to make changes to:
You can use Localist’s Theme Editor to access your platform’s HTML to customize how your event data is presented.
In the Theme Editor you can:
Navigate via Settings > Platform Settings > Appearance, you’ll see the following fields:
| Field | Details |
|---|---|
| SILK Wrapper (Brand Template) URL | If you are using our SILK Wrapper feature, save your wrapper’s URL here. To activate the new wrapper or force an update, select the Refresh Wrapper link below the field. |
| Include Localist Styles | Unchecking this setting will remove all default CSS from the platform. |
| User Help URL | This URL will be posted on your platform’s Admin Dash. |
| Default Date Range | Dictates the time range and amount of events that will be displayed upon selecting a filter so the number on the homepage will always reflect this. Select one of the following:
|
| Show Event Types on Event Items | If checked, the Event Type associated with events will display when events are in lists (i.e. Trending, all events, Filtered pages, etc). |
| Default Map View | Select one of the following:
|
| Logo & Link | If you are not using a wrapper or header/footer template, you can upload a logo here that will display in the top left corner of the default header. The URL entered will be attached to the logo. |
| Field | Details |
|---|---|
| + Add Theme | Click to add a new theme. |
| Name | Name of the themes on your platform. |
| Status | You’ll see either:
|
| Actions | Select one of the following:
|
The SILK Wrapper should not be used with Emphasis platforms. If you adopted Localist after October 2019 or have since upgraded to Emphasis, you should be using the Theme Editor and following our Brand Template instructions.
Start by identifying the wrapper source you would like to use then follow these steps:
All content specific to the page (body) should be removed, so only the head, header and footer remain.
These are automatically added by Localist.
This is automatically added by Localist.
This is added by Localist when you specify your UA number in Global options.
Ensure all references to CSS, JavaScript, images, etc., use complete URLs.
If your wrapper does not support responsive design, you must uncheck Responsive Design in Global Options.
When adding comments to your wrapper file, you must adhere to the following requirements:
Directly after the opening <head>
<!-- LOCALIST COMMENT - START head_tags -->
…your styles/CSS/JavaScript/etc. will be here.
Directly before the closing </head>
<!-- LOCALIST COMMENT - PLACEHOLDER localist_styles -->
<!-- LOCALIST COMMENT - PLACEHOLDER localist_js -->
<!-- LOCALIST COMMENT - END head_tags -->
Directly after the opening <body>
<!-- LOCALIST COMMENT - START before_grid -->
…any code related to your page’s header should start after this.
Directly after the final bit of header code:
<div class="content-wrapper">
<div class="wrapper">
<!-- LOCALIST COMMENT - END before_grid -->
<!-- LOCALIST COMMENT - START body -->
<!-- LOCALIST COMMENT - PLACEHOLDER user_menu -->
<!-- LOCALIST COMMENT - PLACEHOLDER search_bar -->
<!-- LOCALIST COMMENT - PLACEHOLDER top_bar -->
<!-- LOCALIST COMMENT - PLACEHOLDER content -->
<!-- LOCALIST COMMENT - END body -->
<!-- LOCALIST COMMENT - START after_grid -->
</div>
</div>
…any code related to your page’s footer should start after this.
Directly before the closing </body>
<!-- LOCALIST COMMENT - END after_grid -->
Navigate to Settings > Appearance
The URL must be publicly accessible.
Once you select Save Changes a “Refresh Wrapper” link will appear under the wrapper field.
Select the “Refresh Wrapper” link to officially import your new branding. Localist will refresh your wrapper once every 24 hours automatically, but if you need to force an update in the future this link will do the trick.
– HEADS UP –
Here are some helpful troubleshooting tips to try before you reach out to the support team!
All Localist Enterprise licenses include access to a unique staging environment to be used as a testing sandbox. Staging is accessible to Platform Admins by navigating to Settings > Platform Settings > Access the Platform Sandbox (right side box). The Platform Admin will be redirected to the staging environment homepage as an already logged in user.
Nope! It is not possible to sync data from Staging to Production. Any additions and custom modifications will need to be manually copied into your Production platform.
Staging can be used to test branding changes (CSS, HTML, SILK Wrapper, etc) and Feeds. However, please note that if you add a Feed, it will import once but it will not automatically import each night.
If you are not using a Brand Template, Localist provides a Custom CSS interface to make basic customizations of surface-level design elements, such as colors, fonts, or sizes.
If you are editing the theme marked as Active then any changes that are made will be live upon saving.
Controls the overall global styles on your platform. Includes sections for:
| Section | Details |
|---|---|
| Branding | Set global colors for:
|
| Global Interface Colors | Controls link and error message colors for:
|
| Global Fonts | Controls global font family, color, and size:
|
Controls platform-wide colors, borders, and border radius. Sections are as follows:
| Section | Details |
|---|---|
| Links | Set link colors:
|
| Buttons & Pagination | Set colors or borders for:
|
| Channel Header | Controls the Homepage and Channel header area below the search bar:
|
| Dropdowns | Colors and border for dropdown menus across the platform. Includes:
|
| Form Elements | Edit styles for all forms across the platform:
|
| Breadcrumbs | Edit styles for platform breadcrumbs:
|
| Tags | Edit styles Tags on the Event Details Page:
|
| Event Cards | Controls event listing cards. Event Cards are visible on the homepage, Channels, search results, and on landing pages for Places, Groups, and/or Departments. Includes:
|
| Featured Carousel | Set colors for Featured Carousels on the homepage or in a Channel:
|
| Content Meta Data | Controls subscribe options colors:
|
| People Bar | The People Bar appears on event details pages and on landing pages for Places, Groups and Departments. Set colors for:
|
| “Submit Event” Component | Controls the look and feel of the “Planning an Event” component on the homepage or in a Channel:
|
| User Menu | Colors for the user dropdown menu:
|
| Landing Page Headers | Controls colors for landing pages for Places, Groups, and Departments:
|
| Map | Colors for map components on Places, Events, and in the Map component on Channels and/or the homepage:
|
| Event Tabs Link Line | Set the color for the lines below each event tab on your homepage or Channel:
|
| Radii | Set the platform border radius for elements of varying sizes. Element sizes include:
|
This tab contains the global CSS box for the entire platform. Code added here will effectively override any default CSS rules on the platform. Custom CSS allows you to change the surface-level design elements, such as colors, fonts, or sizes. If you’re new to CSS, or need a refresher, we highly recommend http://www.w3schools.com/css for how-to’s, tutorials, and complete lists of available properties.
You can access your platform’s default CSS for mobile view and printing via this URL (if in place, use your custom domain, but if not then use the Localist placeholder): https://customdomain.yourorganization.com/platform/stylesheet.css?expand=1.