Skip to content

Restructure interpretive content #135

Description

@almontg

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.

Metadata

Metadata

Labels

interpretive contentissues pertaining to how interpretive content is displayed and accessedproposal

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions