Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Projects page structure #114

Open
goldfirere opened this issue Aug 30, 2021 · 0 comments
Open

Projects page structure #114

goldfirere opened this issue Aug 30, 2021 · 0 comments

Comments

@goldfirere
Copy link
Contributor

I like that the projects page now has three different sections (Ideation, Proposed, In Progress). But I still think there is some improvement to be found here. For me, it starts by thinking "what will a user want out of this page?" I can think of a few potential use-cases:

  1. Someone wants to know what kinds of projects the HF is engaged in
  2. Someone wants to know more about a specific project the HF is engaged in

I find that the current page doesn't really suit (1) or (2) as well as it could.

For (1), the user wants an overview. The current layout prevents this from happening: the boxes for each project are very large, and my normal browser window shows me only two projects at a time, with a lot of white and gray space. (The user also has to scroll past an enormous "Projects" header and a large "Volunteering" box.)

For (2), the user wants more information about a specific project. Yet most specific projects don't provide a way for the user to get more information or to contribute.

  • For GHC Platform CI, the only link is to the GHC repo, which is not very helpful about this particular project. There are names listed, but a curious browser is likely not going to email Ben or Moritz asking for more information.
  • The Performance Tuning Book links to an empty GitHub repo, still in its "push content here" state.
  • The GHC Performance Dashboards box links again to GHC.
  • The Vector Types Proposal links to Michael's blog post with a link titled "vector types proposal". Is this post currently out of date, given discussion on Discourse? (I honestly don't know, as I'm not following this closely. Maybe the blog post is still the best resource.) And it's perhaps confusing to call it a "proposal" in light of https://github.com/haskellfoundation/tech-proposals/, which is (I believe) the canonical home for HF proposals. And, it's odd for a "proposal" to be linked for a project that's not in the "proposed" state.
  • The Unified Haskell Installer project links to https://gitlab.haskell.org/haskell/ghcup-hs. That link seems inappropriate here, given that it's ostensibly only one of the several ideas that are to be unified. It further gives no information about the actual proposed project.
  • Project Matchmaker links to the matchmaker repo, which contains a sentence describing the project. Linking to the repo here makes some sense, because the project is whole-cloth invention of the matchmaker tool. Yet I would also want a link to some design document and/or motivation for why the HF is working on this.
  • The Text-UTF8 migration just links to the text repo, not to, for example, the accepted proposal describing the exact scope of HF's project.

I think this projects page is of critical importance to the HF. As a casual browser to haskell.foundation, I would first scroll through the top page (https://haskell.foundation) and then click on Projects to learn what the HF is actually doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant