readthedocs / readthedocs/ext-theme

Organizations: add team filter to project list

Open
#201 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Improvement Needed: design decision
Dominant language
HTML
Stars
12
Forks
6
Avg merge
13h 25m
Merged PRs (30d)
1

Description

This is probably another change to the filter in community, but noting here for now. The project filter could have at least a team filter, but most likely an organization filter as well.

This would present two options however.

We probably still do want to list projects that belong to the organization and to the individual teams on the respective detail pages. However, these pages shouldn't be where we link users to when giving the user a list of the projects for the team/organization. That is, users might want to see what projects are associated with a team/org, but for any link like "show me projects associated with this org/team", we probably don't want to be linking deep into the dashboard structure like that.

The second option here could ultimately mean that we don't actually list projects on the org/team listing page but instead just rely on the central page to do this instead. I'm probably fine with the listing existing on both but the filters only being usable on the main listing page.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing project filter in community and the organization and team listing pages. Resolve whether filtering belongs on the central project listing, the detail pages, or both; done means the chosen team and organization project-listing behavior is implemented consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.