"Events" pages are a content type used to create events for the network.  The most recent articles can be found under "Events ". They are displayed in chronological order with the most recently posted news appearing first.

Adding a new Events

• To add a new Events, visit the Content Tab.
• Next, click the "+Add content" button, and then choose the "Events " content type.
• Fill out the page fields as described below:
  • TITLE: Add a page Title. This will appear at the top of the page
  • IMAGE: Add an image for the page. This can be a new media item or an existing one. For more information about image size and quality, please see below.
  • We recommend using images that are least 1600 x 800 pixels (Link to BP) for best quality and the ability to crop if needed. Images smaller than that may appear blurry or pixelated when they stretch to fill containers, such as banners. Images need to be at least 800 pixels wide to fill page width (up to sidebars).
  • TEXT: Add the article content to the text section. This is a rich text section and can include additional images, links, bullets, etc. as needed.
• Once these fields are all filled out, hit the purple "Save" button at the top of the page to save the page.
• You can also add additional content blocks as needed.

Editing Events

• To find an existing Events to edit, visit the Content Tab.
• Next, search for the page by name in the "Title" search bar, or you can choose "Events " in the Content type filter to narrow your choices. Hit "Filter.
• Once you have found your page, click on the title, and then click Edit.
• Make the changes you want on the page, and then click the green "Save" button at the top.

Removing Events

In general, content should be left up on the website for archive and search purposes. However, should the team wish to remove it from the site, they should "unpublish" the page. To do this, unclick "published" while in the "editing" mode of the page, and then hit save. The page will be removed from the live site when it next updates, but will remain in the backend, should staff wish to reference it for any reason.