Move settings into a separate settings-page
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
Use case
As described in #2543, Teams could get their own frontend.
Proposal
To de-clutter this "TeamPage" and turn it into a practical and informational starting point for users, the settings for a team should be moved out of the way, into a separate settings page. Reference could be the settings page of a collective:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing TeamPage and the collective settings page referenced in the proposal. Identify how team settings are currently presented, then move them to a separate settings page so the TeamPage becomes a practical informational starting point and the settings remain available there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100