Improve projects empty state and clarify the differences between projects and workspaces
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Users can be confused about projects and workspaces, as well as how they correlate.
The new project page still mentions the workspaces per project split, which has been removed.
Projects allow you to manage prebuilds and workspaces for your repository.
While the existing relevant docs about Teams & Projects differences are clearer, there's still some confusion around Workspaces & Projects.
See relevant discussion (internal).
Proposal
TBD (To be discussed)
In the meantime, things we could improve include:
- Consider updating the Projects empty state.
- https://github.com/gitpod-io/gitpod/issues/5125
- https://github.com/gitpod-io/gitpod/issues/8385
- ...
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 reviewing the current Projects empty state, the Teams and Projects documentation, and the linked issues #5125 and #8385. The proposal is still TBD, so first establish the intended distinction between projects and workspaces and confirm the scope with maintainers. Done means an agreed scope is implemented and the relevant UI and documentation no longer create confusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100