[RHOAIENG-6321] Home Page Microcopy Updates

[jeff-phillips-18]

Closes: RHOAIENG-6321

Description

Content update for the informational section of the landing page

How Has This Been Tested?

Manually tested

Test Impact

Added e2e test to verify the content is adjusted based on feature availability.

Screen shots

Full features (with model mesh enabled)

Full features (with model mesh disabled)

Pipelines disabled

Model serving disabled

Pipelines and Model Serving disabled

Request review criteria:

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)
• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

/cc @jgiardino

[openshift-ci]

@jeff-phillips-18: GitHub didn't allow me to request PR reviews from the following users: jgiardino.

Note that only opendatahub-io members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Closes: RHOAIENG-6321

Description

Content update for the informational section of the landing page

How Has This Been Tested?

Manually tested

Test Impact

Added e2e test to verify the content is adjusted based on feature availability.

Screen shots

Full features (with model mesh enabled)

Full features (with model mesh disabled)

Pipelines disabled

Model serving disabled

Pipelines and Model Serving disabled

Request review criteria:

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)
• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

/cc @jgiardino

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andrewballantyne]

Content is by Katie, not reviewing it closely. Couple questions about code organization.

👍 nice cleanup on tests.

[jgiardino]

Is it possible to wrap separate paragraphs with separate <p> or <small> elements to get spacing defined via PF styles instead?

[jeff-phillips-18]

@jgiardino It is already in a <small>, would the <br> not be sized as one line height of the small? I can change it to be specified by every caller of the <InfoGalleryItem> rather than in the common component.

[jgiardino]

The rule-of-thumb I've always followed is to use separate <p> tags for separate paragraphs to get the preferred spacing between paragraphs. In this case, the space between would be slightly different if implemented as separate <small> elements vs using <br>. TBH, I'm not sure if there are any a11y implications with using line breaks vs separate <small> elements, so it may just be a cosmetic issue.

[jeff-phillips-18]

OK, I've updated it to use multiple <small> components.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andrewballantyne]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment