Event Feed

• Event Feeds may be used on multiple schemas: You may use Event Feed components on Section Fronts, Section Detail, Profile Detail and Degree Detail pages.
• You may use multiple Event Feed components on page: If your page requires multiple Event Feed components for different event types, you are allowed to publish multiple components to a page.
• You may not combine multiple Event Feed components for a larger, singular event listing: Individual Event Feed components are limited to four (4) events. You may not blend two Event Feed components with the same tag and background color to increase the number of events on a page. Each Event Feed component must have different event types or tagging.

• Static size: The Event Feed has a set size and does not flex to the event information pulled into the component
• Fixed event number: The Event Feed will only display the next four (4) events in your Localist feed.
• You may choose different background colors: The Event Feed allows for gray, blue or silver backgrounds. Consider the look-and-feel of your page (e.g., layout, mobile experience) when selecting a color.
• No WYSIWYG: The Event Feed component does not have a formattable WYSIWYG field. It does have a paragraph-text only description field allowing you to place additional content under the Event Feed Title field.
• Categories are required: When building your Localist event list and widget, remember to categorize your content accordingly. Categories are pulled under the time of the event automatically. If you do not have a category, the field will appear broken on the page.
• Use a call-to-action button: You may place a call-to-action button at the bottom of the component. Use this option to your advantage to get your user interested in clicking through to more of your events (e.g., standalone Localist events page on events.unr.edu).

• Select a proper H- or P-tag for your Event Feed: Be sure to select a proper H-tag for the position of your Event Feed on the page to ensure you do not skip H-tag levels and adhere to our accessibility and on-page optimization guidelines .
• Event anchor text (links) must be unique: Each Event link anchor text must be unique to that link to ensure you do not create a multiple destination link accessibility error. If you are using recurring events in your Localist widget/feed, be sure to use the "Allow Duplicate Title" options in the component. This makes a code update to identify the link as unique to individuals using screen readers or other assistive technology.

EVENT: UNIT NAME - Purpose

• Example: EVENT: OPS - NV Bound