Jump to HeaderJump to Main ContentJump to Footer
Michigan State University
Michigan State University
Digital Experience Studio

University Communications and Marketing

Digital Experience Studio

  • Experience Program
    • Website Project Process
    • Working with a Vendor
    • Glossary
    • Taxonomy Data Dictionary
  • |
  • Experience Design
    • Website Strategy
    • Website Structure
    • Information Architecture and Navigation
    • User-Centered Design Conventions
    • Common UX Issues
    • Enterprise Design System
    • Content Planning
    • Creating Accessible Content
    • Taxonomy and Filters
  • |
  • Website Technology
    • Web Standards
    • Search Engine Optimization
    • Cascade CMS
    • Sitecore CMS
    • Content Hub Basics
    • Content Hub DAM
    • Content Hub Operations

    SitecoreAI

    Sitecore user login
  • |
  • Social Media
    • Alt Text Bookmarklet
    • Meta Ad Pixel
    • Social Media and Web Integration
    • Sprinklr

    Sprinklr

    Sprinklr user login
  • |
  • Analytics
    • Google Analytics (GA4)
    • Testing
    • Data Visualization

    Google Analytics

    Google Analytics user login
  • |
  • News and Events
    • News and Updates
    • Events and Trainings
Digital Experience Studio

University Communications and Marketing

  • Experience Program
  • Experience Design
  • Website Technology
  • Social Media
  • Analytics
  • News and Events

< Experience Program

  • Website Project Process
  • Working with a Vendor
  • Glossary
  • Taxonomy Data Dictionary

< Experience Design

  • Website Strategy
  • Website Structure
  • Information Architecture and Navigation
  • User-Centered Design Conventions
  • Common UX Issues
  • Enterprise Design System
  • Content Planning
  • Creating Accessible Content
  • Taxonomy and Filters

< Website Technology

  • Web Standards
  • Search Engine Optimization
  • Cascade CMS
  • Sitecore CMS
  • Content Hub Basics
  • Content Hub DAM
  • Content Hub Operations

SitecoreAI

Sitecore user login

< Social Media

  • Alt Text Bookmarklet
  • Meta Ad Pixel
  • Social Media and Web Integration
  • Sprinklr

Sprinklr

Sprinklr user login

< Analytics

  • Google Analytics (GA4)
  • Testing
  • Data Visualization

Google Analytics

Google Analytics user login

< News and Events

  • News and Updates
  • Events and Trainings
Digital Experience Studio > Website Technology > Content Hub Operations > Content and Pages >

Custom Stories

MSU Tools and Resources

  • A to Z Index
  • Find People
  • Email
  • Tech Support
  • Social Media Directory

Communications Resources

  • University Communications and Marketing
  • University Trademarks and Licensing
  • MSU Brand Studio
  • MSU Editorial Style Guide
  • MSU Photos

Contact us

517-355-7505

Address

Michigan State University 408 West Circle Drive East Lansing, MI 48824

Follow Us

  • Visit our Facebook page
  • Visit our page on X
  • Visit our Instagram page
  • Visit our LinkedIn page
  • Visit our YouTube page
  • Visit our TikTok page

If you're having accessibility issues, please let us know.

Know MoreTransparency Reporting: Budget & Salary/Compensation
  • Contact Information|
  • Site Map|
  • Privacy Statement|
  • Site Accessibility|
  • Call MSU: (517) 355-1855|
  • Visit: msu.edu|
  • Notice of Nondiscrimination|

SPARTANS WILL|© Michigan State University|

Custom Stories

When to Create a Custom Story

The Custom Story content template in Content Hub is designated for stories that require a unique layout presentation on MSUToday that cannot be made with existing story components.  

The decision to create a Custom Story needs to be made during the planning process, prior to the story being entered in Content Hub.

Criteria for a Custom Story template include:

  • Significant university news or accomplishments
  • Visuals will enhance reader experience  
  • Content requires a unique approach that cannot be achieved using existing components 

Custom Story Workflow

Content Initiation to Pre-Publishing in Content Hub Operations

Custom stories follow the Main Workflow. Like all other stories, the text of the story must be created in a Word document and shared with a link in the Comments section. The story must go through the entire workflow, including the Edit step, before it is available to build. The story becomes available in Sitecore at the Pre-publishing step, at which point all the taxonomy fields must be completed in Content Hub and cannot be changed.  

Once the story is in Pre-publishing, the story author will coordinate with the designer/builder assigned during the planning process. The author, designer/builder and any other appropriate person will work together to select assets from the DAM. Once assets are selected, the author is responsible for writing captions, including necessary credits, and having the captions edited. The author is also responsible for adding alt text in the DAM. 

Custom Story Build in Sitecore

The majority of authors do not have access or the ability to create custom stories in Sitecore. The designer/builder is responsible for moving story text from the Word doc linked in the comments to the custom layout and formatting, as appropriate.   

The designer/builder must manually complete the following fields in Sitecore in Page Builder in either the Page content settings panel or Content Mode:

  • Title (headline)
  • Thumbnail
  • Open Graph

The designer/builder must include the following information in the page layout:

  • Headline
  • Sub-headline (if applicable)
  • Summary (if applicable)
  • Author(s)
  • Media Contact(s) (if applicable)
  • Date  
  • Read time 

Preview and Publish

Preview links created by Content Hub will not reflect the custom layout. To complete reviews, the designer/builder needs to coordinate with the author to share their screen with the preview available in Sitecore, either virtually or in person. The story author is responsible for coordinating and obtaining any other necessary reviews and approvals as appropriate before publishing.  

The author is responsible for selecting “Finalize” and “Publish” in Content Hub. Then, the designer/builder is responsible for deselecting “No Index” and “No Follow” and publishing in Sitecore.  

Both the author and designer are responsible for checking that the story appears correctly in MSUToday on desktop and mobile. 

 

Documentation updated: Sept. 25, 2026

Is there an issue with this documentation? Report it here.