Firstly - congratulations to Matthew Butterick on beautiful design!

Now to the feedback:
1. There is one thing that frustrates me most when I stumble upon new 
website/package/repository for the first time and I have no previous knowledge 
of its content. It is due to the amount of time it takes me to get an answer to 
a simple question: "What am I looking at?". If I can get the answer quicker 
using google search or wikipedia than the website itself is probably missing 
something.
With current design I get the answer as to what it includes (eg. batteries, it 
can run cross-platform) before I can conclude that Racket is probably a 
programming language (and some more cool stuff) although this is never stated 
just inferred. Calling Racket a programming language maybe sells it short but 
at least gives the answer to the question "What am I looking at". Placing 
something like the old "Programming-language Programming Language" somewhere 
near the top may solve the issue.
2. Greyed out code snippets - I am not a fan of too much greyed out text or 
code. It causes unnecessary eye strain. If this has to stay maybe make it not 
AS GREY as it is right now.
3. I understand other pages like documentation (or rather its out of place top 
black Racket bar) and Packages will also have a look overhaul. If that's the 
case than one word: great! Especially that the old Packages (pkgs...) looks now 
terribly outdated
4. [NON-DESIGN] Racket Manifesto link (under "The Best of Scheme/Lisp) gives 
404 error page. I think these most important documents should be placed on 
Racket server to avoid this in the future.

These are just my personal views - feel free to adapt/ignore.

Greg

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to