- Drop the wiki completely - it’s actively unhelpful, and any of us can all publish whatever we want here on discourse, or on github/gitlab/etc elsewhere.
-
Replace the wiki with a complete, and authoritative guide for getting things done in haskell. It should be
- targeting new haskellers
- focused on their onboarding experience (what % converted to “competent and capable haskeller”)
- carrying them through to intermediate and then beginner-advanced levels
- opinionated, focused on reliable/proven best-practices
- inclusive and acknowledge places where alternatives exist
- extensive in topics, covering all the typical scenarios seen in hobby and commercial products
- maintained by the community
- based on and using existing material and prior-art, including for example rust’s, Stephen’s “what I wish I knew”, the retired haskell-lang.org site, etc.
- Make the downloads page stupid-obvious: When a pythonista/PHP/gopher says “I’m going to try haskell”, and goes to haskell . org / downloads for the first time, they should not get stuck/blocked wondering what to do, they should have clear and obvious instructions for their next steps (downloading, and getting started on into docs and code examples, etc).
- Keep available the curated list of tutorials and books/docs/etc - the existing list of tutorials/docs/books is great and should continue to exist, but it needs a new place next to the authoritative guide described above.
Just echoing what I’ve heard others say that I believe makes sense and addresses the problems we have picking up and being efficient with Haskell.