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

Landing Pages for Content Types #134

Open
almontg opened this issue Jan 7, 2025 · 3 comments
Open

Landing Pages for Content Types #134

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

Comments

@almontg
Copy link
Collaborator

almontg commented Jan 7, 2025

Create landing pages for interpretive content types (right now "stories" and "people") which would dynamically arrange content by tags, such that all people tagged "map collector" would appear together, etc, with a basic nav for viewing and skipping to sections.

Would ideally also include options for sort, but this is less important.

@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
@garrettdashnelson
Copy link
Member

@almontg I'm not sure I completely understand this request and I think I could benefit from a visual sketch of what you're after here

@almontg
Copy link
Collaborator Author

almontg commented Jan 10, 2025

Super basically, if a user were to click on "stories" (or people/ARGOpedia) in the top bar, they would be directed a page like this rather than the unfiltered card list they currently get:

image

Key features here are some kind of nav that lets users see all the possible tags/sections, and then the sections themselves; left nav design here is based on how tags are already displayed on individual people pages for visual consistancy.

I'm imaging here that what goes is in each section is determined by the story_type in the frontmatter (for stories) and we could implement something similar for ARGOpedia.

In the sketch I have these as expandable sections to save screen real estate for browsing through everything but that's just a thought; key thing here is to chunk out the content and make it easier for users to browse and find the kind of content they are looking for.

@garrettdashnelson
Copy link
Member

Ah, ok, got it! That makes sense! For the stories section, I wonder if we want to not interrupt the date-of-publication order, and if so maybe it would make more sense for it to be a series of on/off toggles which show/hide certain types of content? We can discuss on Monday.

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
Projects
None yet
Development

No branches or pull requests

3 participants