This task discusses the future direction of project pages. Making a decision here is partially blocked on other work, like T3670: after seeing how it turns out, we'll have a better sense of what we want to do with project pages. We don't expect to make significant changes here in the short term until more influencing work finishes.
Project pages aren't very useful right now. Some specific problems include:
- The information they show is arbitrary (handful of most recent tasks).
- The information they show is incomplete (e.g., no way to get to repositories or mocks or other objects).
- Workboards, which are relatively important and tied closely to projects, are also relatively hard to get to.
- Most information shown on the pages (members, description) and most actions (leave, flag) are rarely used.
Likely directions for project pages include:
- Stepping back from them and building something more broad and general, likely with a high-level focus on status/progress/completion. This would happen after T3670; or
- replacing them with dashboards.
Particularly, it seems very unlikely that the future of project pages is expanding them as they exist today (for example, by adding more hard-coded features). If we decide to go in that direction, it would be simpler and more powerful to do it through dashboards.
(If you want a page showing repositories/tasks/revisions/mocks/etc for a project, Dashboards are almost certainly the best answer regardless of what we end up doing with project pages. Currently, building a dashboard for a project is somewhat cumbersome. We may allow you to explicitly parameterize dashboards in the future, so a dashboard renders for a specific project.)