Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newsletter Archives & Lists #1391

Closed
kevincrafts opened this issue Oct 10, 2024 · 1 comment · Fixed by #1476, CuBoulder/tiamat10-profile#231 or CuBoulder/tiamat-custom-entities#192
Closed
Assignees
Labels
new New feature or request

Comments

@kevincrafts
Copy link
Member

In D7 Express, there's two ways to show previous newsletters:

Archive Page

A paginated list, sorted by most recent, of all newsletters of a specific type. This is not a content type. Just a path that will return the display of newsletters with the titles and summary.

Example: https://www.colorado.edu/today/newsletter/cbt-students

Newsletter List Block

A block can also be created that allows the editor to choose which type and how many (1-10) recent newsletters they want to display. Underneath the list there is a link to the archive page to see more newsletters. The display is the newsletter title and summary.

Example: https://www.colorado.edu/today/newsletter-list

@kevincrafts kevincrafts added the new New feature or request label Oct 10, 2024
@patrickbrown-io patrickbrown-io self-assigned this Oct 15, 2024
@patrickbrown-io
Copy link
Contributor

patrickbrown-io commented Nov 12, 2024

Archive Page

There is an issue. The summary isn't simply a summary field on a Newsletter-- it is the first Article or User-Content in the Newsletter used as a summary. Which means its a paragraph, in a paragraph, in a paragraph, which will have another reference to an Article if its an Article content paragraph. The "summary" grabs that first Article or pseudo-Article title buried in this monster nesting dolls of paragraphs. I don't believe we can dive that deep like that on a View which would satisfy the paginated and not-a-content type endpoint requirement.

Options:

  • Content Type: we do it like the Issue Archive, js saves the day. We would need to manually add these pages. This could get messy as they'd need to create pages for every taxonomy.
  • We could do this as a View without summary field
  • Add a summary field to the Newsletter content type. If thats not filled out, then nothing shows up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment