You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
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.
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.
The text was updated successfully, but these errors were encountered: