-
Notifications
You must be signed in to change notification settings - Fork 96
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
Move the "Try it!" section in favour of a more eye-catching section #259
Comments
I was convinced by @rebeccaskinner that it should be moved instead of removed. I have edited the title of the ticket to reflect this. |
I like this idea. I don't know why we'd keep "Try it!" around now that we have the Playground though. |
@tomjaguarpaw The "Try It!" is fundamentally a tutorial, it that it has clear beginning and end, a set of step to accomplish a goal, and the concrete objective to turn newcomers into users. The playground requires more acquaintance with the language. Now the playground can be the backend for a tutorial, but this is another piece of work. Right now the tutorial is taking space that could be used better. :) |
@idabzo tells us that we should adapt the vocabulary to use less jargon and appeal to outsiders more. |
Fearless Refactoring is certainly something that we want to promote, especially combined to the compiler, the algebraic typeclass laws, etc. |
@Kleidukos , how fluffy is that?: |
Thinking about it, we should move this section and put some concrete advantages of Haskell instead. This is a very important piece of UI real-estate because on laptop and desktop screens, it is displayed without having to scroll.
However the "Features" section is near the bottom, below even testimonials, so reading the page you get people praising things that you don't know about yet, which is a very peculiar way of putting content together.
I suggest that the replacement section should have three practical concepts with an accompanying sentence that drives the curiosity of casual visitors.
I'm thinking of:
The text was updated successfully, but these errors were encountered: