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

Restructure interpretive content #135

Open
almontg opened this issue Jan 7, 2025 · 1 comment
Open

Restructure interpretive content #135

almontg opened this issue Jan 7, 2025 · 1 comment
Assignees
Labels
interpretive content issues pertaining to how interpretive content is displayed and accessed proposal
Milestone

Comments

@almontg
Copy link
Collaborator

almontg commented Jan 7, 2025

This is more of a proposal rather than issue but putting it here to keep it all together; this supercedes #98 so I'm closing that issue, but depending on how we want to move forward with this this will likely spin off other more concrete issues to address.

We all know this needs to happen, here is my proposal. See also #134 which addresses the need to create landing pages which would make it easier for users to navigate within these proposed content types.

Three non-map content types:

ARGOpedia
More informational pieces, generally authored by students; this includes the “people” pages, the structure of which would be the model for these, and the “event” pages which are currently in stories.

“Stories”
Would include scholarly blog posts, live events, etc

Classroom materials/teacher guides
Structurally will be very similar to the other content types and do not require anything special but should live in their own folder hierarchy.

Question: how would we want to deal with exhibits within this proposed hierarchy? I could see them either being a tag subset of stories or their own category as long as we define them fairly tightly.

@almontg almontg added this to the milestone-4 milestone Jan 7, 2025
@almontg almontg added the interpretive content issues pertaining to how interpretive content is displayed and accessed label Jan 7, 2025
@emilyrbowe
Copy link

emilyrbowe commented Jan 13, 2025

Discussion output:

  • "ARGOpedia" would be a top-level landing page that brings together "People", "Moments/name TBD", etc, but we would need to standardize the content layouts for some of the nested content. All student work would end up here.
  • /stories would contain the Articles (renamed from "story), Interactives, Talks (renamed from "Live Events"), and Gallery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interpretive content issues pertaining to how interpretive content is displayed and accessed proposal
Projects
None yet
Development

No branches or pull requests

4 participants