Web

Events Detail Template

Style Guide

Citizen Science A volunteer examines a 'beard-tongue' flower (Penstemon sp.) at The Nature Conservancy’s Red Canyon Ranch Bioblitz event. © Timothy Rockhold

(Pg. 5 document link above

Always Use the Event Details Template for Events

Any event or volunteer event that you want to post and promote on nature.org should have an Event Details page. Using the template has the following benefits:

  • Events that use the template are searchable through the global Find Events and Opportunities page.
  • Events that use the template can be automatically pulled onto state homepages and preserve pages using the related events component.

There may be very limited special cases where additional supplemental content needs to go on another page in addition to the Event Detail Template, but that additional page should not substitute for an Event Detail page, and you will need publisher approval to create such a page.

Examples of Event Pages:

Find events here: https://www.nature.org/en-us/get-involved/how-to-help/events/

Special Cases—event series or recurring events

For SEO reasons, please avoid posting multiple event pages that are identical or nearly identical. For events that repeat on multiple days, follow these guidelines:

  • Create a single page that covers all instances of the event.
  • Assign that page a range of dates (from the first instance to the last), and list the individual instances/dates in the body of the page.
  • Whenever possible, mention the dates or the range of dates in the event description so that that information comes up on event cards and search results. (Mentioning all individual dates becomes impractical for 5 or so dates or more, so in that case mention that the event occurs on a range of days.).

Examples of Combined Events:

Tennessee Webinars

Little Jerusalem Badlands Guided Hikes

Early Birder Days

*Event pages expire after the event, so please excuse any broken links here.

Special Cases—tabs on complex event pages

For conferences or special events that require posting large amounts of detailed information, the tab container can now be used in the Event Template. Put the Event Details Component in the first tab and RTEs in subsequent tabs for supporting information.

More details and examples will be added as we gain experience with this use case.

Examples of Complex Events:

To come…

*Event pages expire after the event, so please excuse any broken links here.

Properties: The following properties tabs must be filled in. Ignore the other tabs.

BASIC TAB

  • URL: This field will be used to auto-generate the URL. For new pages, always include the state name for SEO purposes. No need to change any existing URLs. Example: “new-york-tree-planting-x-preserve”. The URL will be cut off at 64 characters, so keep your URL shorter than that or words will get cut off. Format as a URL with dashes between words and do not include captial letters, underscores or other special characters (besides dashes).
  • Owner or Business Group: Make sure you designate the state (or country) as the Business Group. Use only one business group. 
  • Page Title: Appears on the browser tab, and more importantly, is the headline you’ll see in search results, pulled onto cards in the related events component and on the global event search page. You don’t necessarily want to include the state name in this title (if you include it on every event, it will get repetitive in related events listings), but some clues to location in the title or description will be helpful to users.
  • Description: This is the promotional text you’ll see in search results, pulled onto cards in various components, and on the global event search page. Keep this to one sentence (150-160 characters maximum) and describe the basics of what the event is about.
  • On Time and Off Time: Make sure you leave these blank. The Off Time will auto-populate to make the page expire the day after your event end date.

IMAGE TAB

The image path you use here will dictate which image loads on cards and on the map on the PWP landing page. Remove special character from image filenames before uploading them to the DAM.

OG and SEO TABS

Follow the general instructions here and any SEO guidance to come.

EVENT DETAILS TAB

Follow the instructions on slide 12 of the “Page Properties by Template” guide from GD. For a recurring event, the end date should be the last day of the series. Contact your publishers if you have questions about or issues with the event date and time fields or setting up a recurring event.

Event Pg Properties

Page Creation (2 Tabs)

  • This is the end portion of the URL of the page. Enter a URL in this field in URL format. Example: this-is-a-url-example. The URL field should contain ONLY lower case letters and numbers and dashes. Spaces and special characters are not allowed. Make sure you are happy with the page URL as it is very difficult to change. 50-character limit.

  • Page Title should be written for external audiences and displays on page cards, internal search results, breadcrumbs (if applicable) and in components when the title is not authored directly. 150-character limit.

  • This should be an enticing sentence or two about what readers will find on this page. It will be used on page cards and in internal search results. 

  • Select Event. The content type for all pages in the Event detail template should be "Event." 

  • This should be the BU or department that is the primary owner of the page. This field will be used for aggregation pages, analytics tracking, and will allow you to easily locate all of your pages for internal review or audit.

  • Select at least one audience tag that best describes the target audience of your content. Choose the broadest audience that would benefit from the goals of your page. 

  • Required. Select one location or two (if applicable). If global/virtual event, select “all locations."

  • Enter the name of the person(s) who should recieve notifications if a link or asset on the page is expiring - or if the page itself is set to expire.

Basic Tab

  • COMPLETED IN PAGE CREATION STEP. Page Title should be written for external audiences and displays on page cards, internal search results, breadcrumbs (if applicable) and in components when the title is not authored directly. 150-character limit.

  • Optional. The only place this will used is as the subtitle in hero components if a custom subtitle is not entered in the component. 

  • COMPLETED IN PAGE CREATION STEP. This should be an enticing sentence or two about what readers will find on this page. It will be used on page cards and in internal search results. 

  • If the page is available in more than one language, enter the language of the current page in this field. 50 character limit. 

  • Enter the page path for the current page (the page in the language indicated in the previous field).

  • If the page is available in a different language, enter the name of that language here (in the native language - e.g. Español). 50 character limit.

  • Enter the page path for the alternate language version of the page (the language indicated in the previous field).

  • Checking this box will hide any active site-wide alert banners from displaying on your page. This may be used at your discretion, but is not generally recommended.

  • Checking this box will remove the social share buttons from the page. This may be used at your discretion but is not generally recommended.

  • Do not use this checkbox unless instructed to do so by global marketing teams.

  • Use the calendar icon to schedule a date and time for the page to go live once it is published. If none is selected, the page will go live automatically after workflow is complete. You can also select publish time when submitting your page for publishing. 

  • For non-evergreen content, enter a desired expiration date (off time). 

Image Tab

  • Required. Select an image to display on the page cards. This image will be pulled onto the page card in the following components: related events, search and featured content.

  • Enter a description of what is shown in the page card image selected in the field above. Alt text is critical to making the page accessible to all audiences. 

  • This field instructs AEM on how to crop the photo to fit the aspect ratio needed for desktop browsers. Select the section of the photo to maintain during cropping. (E.g., selecting Top/Left will maintain the top left corner of the image and will only crop as needed from the bottom and right sides)

  • This field instructs AEM on how to crop the photo to fit the aspect ratio needed for mobile browsers. Select the section of the photo to maintain during cropping. (E.g., selecting Top/Left will maintain the top left corner of the image and will only crop as needed from the bottom and right sides)

OG Tags (Social Share)

  • Enter a title for the social post. This will appear on social share card generated when someone shares the page link on social media.

  • Enter a short description. This should be an enticing sentence or two about what readers will find on this page. It will show on social media posts that generate from sharing page link.

  • Choose the most appropriate page type. Most pages that are not in the article template should be categorized as 'website.' Search engines need this piece of info to recognize pages. 

  • Required. Select an image to display when a social media post is generated from the page link.

  • Optional. Enter the relative URL for the page. Field determines the address that the social post will link to.

  • OG site name determines the source that displays on social posts. For pages on the TNC global English site, the field should read 'The Nature Conservancy.'

SEO Tab

  • This is what is seen in the browser tab and Google search results. Should be a shorter version of the page title and include high value words. If you have enough room, include branding at the end of the title: | The Nature Conservancy OR | TNC (though don't sacrifice important words to fit the branding in). 65 character limit.

  • This description is visible in Google and other external search engine results. It should primarily entice people to click on the page: what is the page about, why should people want to read it. 170 character limit.

Event Details tab

  • COMPLETED IN PAGE CREATION STEP. Select Event (should default to event). 

  • COMPLETED IN PAGE CREATION STEP. This should be the BU or department that is the primary owner of the page. This field will be used for aggregation pages, analytics tracking, and will allow you to easily locate all of your pages for internal review or audit.

  • Optional. If applicable, select secondary business groups to be used for sorting and filtering. If the event should appear connected with other business group(s) in search, filtering, and sorting, additional business group or groups should be entered here. This field is optional and multi-select. 

  • COMPLETED DURING PAGE CREATION STEP. Select at least one audience tag that best describes the target audience of your content. Choose the broadest audience that would benefit from the goals of your page. 

  • Required. Enter the title of your event. 

  • Required. List the general location of the event. Recommended formatting: [Location Name], [City], [State]; or [City], [State]. Example: Fraser Preserve, Fairfax County, VA. It will be shown on event cards. 35 character limit.

  • Select “public” if you want event to be visible and aggregate with other events. If you select “private” your event will not come up in search and you will have to link to it directly.

  • Required. Enter or select the date that the event starts. Details will show up on event detail page.

  • Required. Enter event start time – or check “All day event”. Time uses a 24-hr clock. Details will show up on event detail page.

  • Enter or select the date on which the event ends. Details will show up on event detail page

  • Enter event end time – or check “All day event”. Time uses a 24-hr clock. Details will show up on event detail page

  • Required. Select the time zone. This is a display field and will not affect the time entered in other fields.

  • If you select “yes”, enter the recurrence information in the next field.

  • Select how frequently the event occurs from the dropdown. 

    For example, if you have an event that occurs every other month on the third Wednesday of the month, you would set the: 

    "Recurring Event?" field to Yes  

    "Repeats" field to Monthly

    "Every X Day(s), Week(s), Month(s)" to 2

    "Select Day of the Month" field to Third 

    "Select Date" field to Wednesday. 

  • Select how frequently the event occurs using the plus and minus buttons.

    For example, if you have an event that occurs every other month on the third Wednesday of the month, you would set the: 

    "Recurring Event?" field to Yes  

    "Repeats" field to Monthly

    "Every X Day(s), Week(s), Month(s)" to 2

    "Select Day of the Month" field to Third

    "Select Date" field to Wednesday.

  • Select how frequently the event occurs using the dropdown.

    For example, if you have an event that occurs every other month on the third Wednesday of the month, you would set the: 

    "Recurring Event?" field to Yes  

    "Repeats" field to Monthly

    "Every X Day(s), Week(s), Month(s)" to 2

    "Select Day of the Month" field to Third

    "Select Date" field to Wednesday.

  • Select how frequently the event occurs using the dropdown.

    For example, if you have an event that occurs every other month on the third Wednesday of the month, you would set the: 

    "Recurring Event?" field to Yes  

    "Repeats" field to Monthly

    "Every X Day(s), Week(s), Month(s)" to 2

    "Select Day of the Month" field to Third

    "Select Date" field to Wednesday.

  • Suggested. Will be an event, or activity, or will have a focus (green cities). Focus on top 1 or 2 for each L1. (i.e. one event type, one activity type, one conservation work type if applicable, one species if applicable) No more than 5-6, 1-3 recommended.

  • COMPLETED IN PAGE CREATION. Required. Select one location or two (if applicable). If global/virtual event, select “all locations.

  • If event occurs at a place TNC protects, select that place.

  • COMPLETED IN PAGE CREATION. Required. Enter the name of the person(s) who should receive notifications if a link or asset on the page is expiring - or if the page itself is set to expire.

Event Page Components

There are four configurable sections of the Aggregation Automated page template and each section allows for a specific components. Below are the sections and components available to use in each section: 

Configurable Sections      Available Components
Hero C09 Hero Image
Body

C50 Event Details

C19 Tab Container

C111 Image Mosaic

C105 Statistics Component

Within Tab Container

C20 Rich Text Editor (RTE)

C23 Featured Number List

C24 Map

C38 Image

C38 Image Collage

C50 Event Details

Ending

C11 Title Text CTA 

C26 Media Gallery

C27 Related Articles

C27 Related Articles (Auto)

C38 Image

C39 YouTube Video

C70 Callout

C88 Partner Brand

C111 Image Mosaic

C121 Image Collage

 

Additional Aggregation Auto Page Examples

To view an example page built in the Event Detail page template, click the link at the bottom of this paragraph. The link will bring you to a page on the online application Invision. On the page, turn on comments in the banner on the bottom right hand corner of the page. With the comments on, you will see that each component is labeled. Click on the hotspots to see the name of the component used to build the page. 

EVENT PAGE EXAMPLE LINK 

Ready to publish? Need guidance on publishing and workflows? Check out the publishing and unpublishing resources

Questions?

Current Updates

Hello Authors and Publishers,

There are now many additional components allowed on the Event Detail page and there have been recent style updates to the Events Detail component. If you have questions about how best to design/configure your page please reqch out to your publisher! 

 

Updates for C50 Event Detail

What else has changed: You will now see two additional fields in this component. Currently, the first field you will see is labeled “Has the user RSVP’d?*”. If the field is set to “NO” then you will not see any difference on the event page. If the field is set to “YES” then you will see a message above the event description that reads “You RSVP’d to this event.”

You should NOT set this field to “YES” on any page on Nature.org. This field is for portal use only.

The second new field you will see is labeled “Is this an event or trip?.” You can ignore this field entirely. It will have no impact on the page.

Questions? Reach out to your AEM publisher or the Marketing Requests Portal