I deleted my bikeshedding of each of the sites, and want to focus on
Nim's, which seems a good influence to consider, for tweaks to the
current draft Racket page. Then I have a couple additional general
comments.
https://nim-lang.org/
Nim's does a good job of being clear there are 3 ideas -- starting with
the top heading (above the blurb that starts to anchor Nim to familiar
terms), and then using those same 3 ideas keywords for what reader might
recognize as 3 subheadings below, maybe without much/any scrolling.
Though they're trying to fit a lot less stuff than the draft Racket page is.
Notice Nim's 2-column layout with the expansion of 3 ideas on the left,
and the code examples all on the right. This is responsive/adaptive
layout, so when the window on a small screen or too narrow, all the code
examples get bumped to the bottom of the page, to after the elaboration
of the 3 ideas.
As much as I like Nim's, they also have a bit of a problem of too many
conceptually-overlapping confusing navigation paths in their top nav
bar: Blog, Features, Download, Learn, Documentation, Forum, Donate,
Source. Elixir's is worse. Racket does the top nav bar better than
either. Though Racket also has a similar problem in other regards, and
much worse (e.g., see the documentation index that's impressing with
sheer number of manuals rather than at-a-glance clear path and
organization, or the atrocity page of umpteen different ways to access
the email lists.)
Separate from Nim's, I just clicked on some more of the subtopic buttons
in the draft Racket page, and come of the content behind them is weak or
poor examples, though some is strong, IMHO. For example, the very first
link, you see if you click on the first button of the first idea
(presumably one of the most important things), is for a package system.
(A language platform making its own package system has become almost a
joke of compulsive NIH, and maybe a lesser checkoff item, no longer a
top selling point.) Depending how much of these you could cull and
consolidate, maybe you don't need the JS part, and can get by with all
text always visible.
Also, I'm not sure we should say "batteries included". Racket has a lot
of stuff, but it's ordinary to have to DIY modules that are
off-the-shelf in platforms that were saying "batteries included" before
Racket did. Racket is batteries-included relative to R5RS, not to
more-popular languages. We can reach out to Scheme people a different
way (perhaps including R7RS support), but the Web site presumably is
targeting a much larger audience familiar with some of the most popular
languages.
--
You received this message because you are subscribed to the Google Groups "Racket
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/3ca1df36-876d-e085-f4e7-8c5db877a462%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.
