This procedure is intended for Page Designer administrators who need to highlight an existing Patient Story, primarily on the Patient Stories overview page.

The component does not create the Patient Story itself. The Patient Story must already exist before it can be selected and displayed through this component.

Component Objective

The Patient Story Highlighted Article Component displays an existing Patient Story as highlighted content.

Its intended use is primarily on the Patient Stories overview page, where a selected story can be given greater prominence.

The component is particularly suited to being positioned toward the top of the page as a featured Patient Story.

Primary Use Case

The recommended use is:

Patient Stories overview page → Highlighted Patient Story

The component allows one existing Patient Story to receive greater prominence within the overview experience.

It should therefore be understood as a highlighting/retrieval component, rather than a component used to build or write the Patient Story itself.

Existing Patient Story Required

The Patient Story must be created before configuring the Patient Story Highlighted Article Component.

The logic is similar to the FAQ Section:

Create the underlying content first → retrieve that existing content through the component

The component cannot be used as the starting point for creating the Patient Story.

This means the administrator should first ensure that the intended Patient Story page exists and is available for selection.

Article Selection

The component configuration is intentionally very limited.

The administrator selects the existing Patient Story through the Article field.

Once selected, the component fetches that Patient Story for display.

The visual presentation is handled by the component rather than being manually recreated within the component configuration.

Design Freedom

The Patient Story Highlighted Article Component provides very little design configuration.

Its purpose is not to allow administrators to redesign the Patient Story presentation.

Instead, the administrator's primary decision is:

Which existing Patient Story should be highlighted?

The component then handles its predefined presentation.

Recommended Placement

The Main Region is the recommended placement for this component.

The component already includes its own embedded margins, so there is no need to place it inside a Boxed Layout simply to introduce page margins.

Recommended structure:

Main Region

↓

Patient Story Highlighted Article

This allows the component to use its intended presentation without introducing unnecessary additional layout structure.

Boxed Layout Is Not Required

Do not automatically wrap the Patient Story Highlighted Article Component in a Boxed Layout.

The component already provides its own embedded margins.

Adding a Boxed Layout simply for margin management is therefore unnecessary.

Recommended Page Context

The component is primarily intended for the Patient Stories overview page.

This is the context in which its use is most strongly recommended.

It can provide a selected Patient Story with additional visibility before visitors continue exploring the wider collection of stories.

The component should therefore be treated as a specialized Patient Story highlighting tool rather than a generic article component to distribute throughout unrelated pages.

Recommended Position Within the Page

On the Patient Stories overview page, the component is particularly appropriate toward the top of the page.

This supports its role as highlighted content.

The selected story receives greater visibility before visitors continue through the remainder of the Patient Stories experience.

Versatility

The Patient Story Highlighted Article Component has a specific and focused purpose.

It:

• Retrieves an existing Patient Story
• Gives that story greater prominence
• Uses a predefined presentation
• Is primarily intended for the Patient Stories overview page

Its limited configuration is intentional.

The component is not intended to function as a generic article builder or highly customizable content block.

Create the Patient Story First

The Patient Story must already exist before it can be selected through the Patient Story Highlighted Article Component.

Do not start with the Highlighted Article Component if the underlying Patient Story has not yet been created.

The Component Does Not Create Patient Stories

The Article field retrieves an existing Patient Story.

Content creation and content highlighting are separate steps.

Main Region Is Recommended

Place the component directly in the Main Region.

The component already contains its own embedded margins.

Do Not Add a Boxed Layout Just for Margins

A Boxed Layout is not required to provide margins around this component.

Avoid adding unnecessary layout structure when the component already manages this aspect of its presentation.

Design Configuration Is Limited

Do not select this component expecting significant visual customization.

The component provides a predefined presentation of the selected Patient Story.

Prefer the Patient Stories Overview Page

The Patient Stories overview page is the primary and recommended context for this component.

Use caution before placing it elsewhere simply because another Page Designer location may technically accept it.

1. Identify the Patient Story to Highlight

Determine which Patient Story should receive additional prominence.

The selected story should already exist before configuring the Highlighted Article Component.

2. Confirm That the Patient Story Page Exists

Before adding the component, confirm that the intended Patient Story page has already been created and is available for selection.

Remember the dependency:

Patient Story first → Highlighted Article second

If the underlying Patient Story does not yet exist, create it before continuing with this component.

3. Open the Patient Stories Overview Page

Open the Patient Stories overview page in Page Designer.

This is the primary recommended context for the Patient Story Highlighted Article Component.

4. Determine the Position of the Highlighted Story

Choose where the highlighted story should appear.

The component is particularly suited to a position toward the top of the Patient Stories overview page, where it can provide greater prominence to the selected story.

5. Use the Main Region

Add the component directly to the Main Region.

A Boxed Layout is not required because the component already contains its own embedded margins.

Recommended structure:

Main Region

↓

Patient Story Highlighted Article

6. Add the Patient Story Highlighted Article Component

Locate Patient Story Highlighted Article in the Page Designer component list.

Drag and drop it into the required position in the Main Region.

Open the component configuration.

7. Select the Existing Article

Locate the Article field.

Search for and select the existing Patient Story that should be highlighted.

The component retrieves the selected Patient Story rather than requiring the administrator to recreate its content.

8. Review the Selected Patient Story

Confirm that the correct Patient Story appears in the Article field.

Because the component provides limited design configuration, article selection is the key administrative decision within the component itself.

9. Review the Page Structure

Before saving, confirm that:

• The selected Patient Story already exists.
• The correct Patient Story has been selected.
• The component is being used as highlighted content rather than as a Patient Story creation tool.
• The component is positioned appropriately within the Patient Stories overview page.
• Main Region is being used as the preferred placement.
• An unnecessary Boxed Layout has not been added simply to create margins.
• The component's predefined presentation is appropriate for the intended use.

10. Click Apply

Once the correct Patient Story has been selected, click Apply to save the Patient Story Highlighted Article Component.

11. Validate on Staging

Validate the completed Patient Stories overview page on the appropriate staging storefront.

Confirm that:

• The correct Patient Story is displayed.
• The highlighted story appears in the intended position.
• The component's embedded margins display correctly.
• The component integrates naturally with the surrounding overview-page content.
• The highlighted story receives the intended level of prominence.
• The component displays appropriately across the required responsive views.

The key principle is:

Create the Patient Story first, then use the Patient Story Highlighted Article Component to fetch and highlight it. For its intended use on the Patient Stories overview page, place it directly in the Main Region and let its embedded margins handle the presentation.