The options below are available as content sub-types under Stories.
Standard Template, Main Workflow
Can be used when the story does not fit any other story type. Often used for stories that are not going out as news releases, are not being pitched to the media and don’t meet the criteria for a feature story. The author must manually select for this type to appear on the Releases and Statements page.
Standard Template, Main Workflow
MSU experts share information on a particular topic in a Q&A style. This type will automatically appear on the Releases and Statements page. The author must manually select the Ask the Expert collection. Select the Faculty and Staff topic as the secondary or tertiary topic. Consider MSU Research as a secondary or tertiary topic.
Standard Template, Campus Story Workflow
Reposting of a story from a partner website or publication, typically sent to us via the comms.content@msu.edu inbox. This is not for original UCAM content. It will often include a note that “This story originally appeared on (website).” Exceptions include when the story fits in a different story type such as Voices/Views and Ask the Expert. The author must manually select for this type to appear on the Releases and Statements page.
Brief Template, Main Workflow
A list of MSU experts who are available to comment on a particular topic that is shared with media. This type will automatically appear on the Releases and Statements page. It will not appear on listing pages, including collections, or in related stories. Consider MSU Research as a secondary or tertiary topic.
Custom or Robust Template, Main Workflow
Feature stories are pre-identified as fitting the criteria for UCAM planned strategic content. Examples include stories connected to paid campaigns, signature projects (typically created based on a high-affinity moments of the year), planned features, ongoing (or “drumbeat”) features, multimedia news features, young alumni stories, and research for you (beneficiary based) stories. The decision to use a custom or robust template must be made before the story is created in Content Hub. Authors must manually select for this type to appear on the Releases and Statements page.
Brief Template, Main Workflow
An invitation for reporters to attend an event. This type will automatically appear on the Releases and Statements page. It will not appear on listing pages, including collections, or in related stories.
Standard Template, Main Workflow
Used to share announcements, research findings and other news with reporters as well as other audiences. In addition, this type is typically sent to media via email and/or a media distribution platform. This type will automatically appear on the Releases and Statements page.
Photo Gallery Template, Photo Gallery Workflow
This is specifically for when the story is a photo gallery. When including a photo gallery in all other story types, add as a component. The author must manually select for this type to appear on the Releases and Statements page.
Brief Template, Statements Workflow
Only the issues team has access to create and publish a statement. This type will automatically appear on the Releases and Statements page. It will not appear on listing pages, including collections, or in related stories.
Standard Template, Main Workflow
First-person narratives that share an individual’s experiences at MSU. Select faculty, graduate, staff or student as appropriate. There are collections associated with each type of Voices/Views that the author must manually select. For student views, always include Student Life as a topic, typically the primary topic. For faculty voices, always include Faculty and Staff as a topic, typically the primary topic. The author must manually select for this type to appear on the Releases and Statements page.
Standard Template, Podcast Workflow
This was created specifically for the MSU Today podcast. The workflow and template will need to be reconsidered for any future podcasts. The author must manually select for this type to appear on the Releases and Statements page.
Documentation updated: Sept. 25, 2026
Is there an issue with this documentation? Report it here.