-
Notifications
You must be signed in to change notification settings - Fork 221
Information hierarchy
smichel17 edited this page Oct 10, 2017
·
1 revision
Hopefully the following process will be useful to figure out how to set up the navigation for a project, for #681.
- List all the information about a project and actions we'd like to present.
- This structure should be as flat as possible. For example, everything in the
About
tab is at the top level, because they don't depend on being in that tab to make sense. - Contrast: the label of an issue doesn't make any sense outside the context of a list of issues (although the list of labels does).
- This structure should be as flat as possible. For example, everything in the
- Sort the items at each level by importance.
- If there are too many items to display them all at the top level, start grouping related items to push them to a lower level.
- Prefer creating groups from items that are near to the bottom and have no sub-items.
- Repeat this step as necessary until you can fit everything into some kind of navigation
- This is also the step to be thinking about what kind of navigation would make sense
I've done an initial attempt at the first step. I've probably missed some things; please, add them -- that's why I made this as a wiki page.
- Name
- Action: [Un]bookmark
- Action: Share
- Action: Open in (browser)
- Blurb
- Language
- Stars
- Action: [Un]star
- Watchers
- Action: [Un]watch
- Forks
- Action: Fork
- Current README in
master
- Contributors
- Activity
- Wiki
- Releases
- Downloads (can these all also be accessed through releases?)
- Action: Search code in repo (can this be made to search the repo at an arbitrary commit?)
- Action: Change branch/tag
- Branch/Tag/Commit
- Action: Share
- Action: Open in (browser)
- Files (on a commit, this is like the web UI's
Browse files
button at the top right of a diff)- Action: Share
- Action: Open in (browser)
- Action: Search in
- Action: Print
- Setting: Wrap lines
- History
- Action: Download code as zip
- Commits (currently awkward from a commit; you can kind of do it by viewing the diff, then the whole file at the time, then the file's history)
- [Commit only] Diff
- [Commit only] Comments
- Issues
- Open/Closed status
- Milestone
- Label
- Project
- Assignee
- Anything else you can filter by
- Action: Open a new issue
- Pulls
- All the same things as issues
- Action: Open a new PR