SDSS-586: Related Content

[buttonwillowsix]

READY FOR REVIEW

Summary

-bi-directional display for related content
-prep for other uses of related content like Explore More on news
-foundation of work will also addresses several other long-standing tickets (that work will be contained in a separate PR)

Review By (Date)

-Required by end of FY24 (August 31, 2024)
-Would prefer July release if possible to enable Woods sitebuilding efforts on new sites

Criticality

Important!

Review Tasks

Setup tasks and/or behavior to test

Testing basic display of related content

1. Check out this branch
2. Create a bunch of people, basic page, news, events, and pub content.
3. Create a Basic Page (let's say it is called "FIND ME BASIC!") and select a wide variety of content to be related (events, people, news, basic pages, pubs)
4. Go to a related event, basic page, news, person, and events pages. Put a Lists paragraph on there and try the "This page related to - All" paragraph or "This page related to - Basic Pages" to see the "FIND ME BASIC" as a list item.
5. Repeat for an Event, News, and Person
6. Go back to "FIND ME BASIC!." Throw a Lists Paragraph on the page and select "Related Content" and then clone to try all the "Related From this Page..." variants.
7. Verify that the expected related content shows up
8. In all cases verify that the sort order is what you'd expect. See https://sdssuserguide-prod.stanford.edu/build/creating-content/related-content-coming-soon for documentation on expectations.

Front End Validation

This uses existing front-end patterns. Nothing new to see!

Backend / Functional Validation

Code

• [X ] Are the naming conventions following our standards?
• Does the code have sufficient inline comments?
• Is there anything in this code that would be hidden or hard to discover through the UI?
• Are there any code smells?
• Are tests provided? eg (unit, behat, or codeception)

Code security

• [NOPE] Are all forms properly sanitized?
• [NOPE] Any obvious security flaws or new areas for attack?

General

• [NOPE] Is there anything included in this PR that is not related to the problem it is trying to solve?
• [ I HOPE SO] Is the approach to the problem appropriate?
• NOTE: Some of the edit forms for content could be improved so this is in a consistent place

Affected Projects or Products

• This will affect People and News, primarily. Handy also for many uses.

Associated Issues and/or People

• SDSS-586
• SDSS-297