Once the Word document version of the content has been finalized and approved in Content Hub Ops, the next step is to transfer the content into Content Hub’s data fields. This step ensures that the story is structured properly for publication and can be enriched with metadata and media.
Authors should copy and paste the final version of the story from the Word document into the appropriate fields on the left side of the content details page. The available fields vary depending on the content sub-type and content template, but can include single-line text boxes, multi-line rich text editor (RTE) boxes, in-line components (including quote, photo carousel or in-line image), a hero image, thumbnail image and an open graph image.
To view a sample of a fully loaded content item, view the “Loaded Text Example page.”
Some templates allow for including an in-line component below the first text box rich text editor (RTE) field. An in-line component is a reference to another content item of a specific type, such as Carousel, Quote or In-line Image, that is rendered in MSUToday in a special way.
When loading a story layout, content authors can, where available, load an existing in-line component or create a new in-line component. See “Add an In-Line Component,” below, for more information. Content authors are required to first create and publish their Quotes, Carousels (including the Carousel Cards) and Images before publishing their full story.
Note: When working on a story that includes In-line Components, such as Carousels, Quotes or In-line Images, make sure to always publish the components prior to publishing the whole story to MSUToday. Otherwise, the content author will have to repeat the publishing workflow for the story to include all in-line components within.
At this stage, all text is copied over from the Word document and all related assets, such as images or media, should be added to the content item. Assets must be loaded into the Content Hub DAM first and then linked to the content item by selecting them through the “Insert Image” action in a rich text editor field.
Follow the instructions below to complete the necessary field(s) for the content item.
Note: This is a rich text component, meaning text formatting is available. Click the three vertical dots icon at the right end of the toolbar to open a menu with additional formatting options, including bulleted lists.
Text boxes are rich text components, meaning formatting is available. These boxes can also include images, videos and podcast embeds (see below for more information).
Some template layouts include one text box, while others include two text boxes with an in-line component placeholder between. The latter layout allows for including an additional content item, such as an in-line image, carousel or quote, between two blocks of text. Only one in-line component can be used within these templates.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
Tip: It can be challenging to work with text and code within the same text box. Create the content that will come before and after the podcast first and embed the podcast code after the text is in place.
In another tab or window, locate the video to be included in the content item. Copy the video URL.
Tip: To easily add space before or after the video, making it possible to continue adding text, hover over the video image until a blue or yellow arrow appears. Click the arrow to add a blank line above or below the video.
Tip: Carousels are made up of cards. Building a carousel card nested within a carousel nested within a story layout can get confusing when the user interface is similar for all. Refer to the label at the top of the content item details page to confirm what content item (i.e., card, carousel or story) is being edited and save often.
Note: The Carousel Headline and Carousel Description fields do not appear in a live story on MSUToday. These fields are optional.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
While this field is a rich text component, it should only be used to add an image. Any text added here will not appear on the live MSUToday story. The layout mapping expects only a single image in this field and ignores anything else.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
While this field is a rich text component, it should only be used to add an image. Any text added here will not appear on the live MSUToday story. The layout mapping expects only a single image in this field and ignores anything else.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
While this field is a rich text component, it should only be used to add an image. Any text added here will not appear on the live MSUToday story. The layout mapping expects only a single image in this field and ignores anything else.
See "Creating Public Links" for more information, including screenshots, regarding building public image links.
After all content and media have been entered, the content author is ready to enter the next state: Validate Taxonomy. Click the Confirm Taxonomy button at the top right corner of the content item details page, indicating that the content item layout is final. All that is left is confirming metadata and preparing for publishing.
While loading the story, make sure to click the “Save” button regularly to avoid losing progress. Content changes do not save automatically.