> On Dec 23, 2016, at 6:55 AM, Greg Trzeciak <gtrzec...@gmail.com> wrote: > > 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?".
We will be adding something like that shortly. > 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. I darkened them a bit. But grey text has been used in screen interfaces for 30 yrs to indicate de-emphasis, and is widely used on today's web (e.g. Github). That particular horse is long out of the barn. > 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 Docs has been updated. Pkgs soon. > On Dec 24, 2016, at 6:05 PM, George Neuner <gneun...@comcast.net> wrote: > At the top of the #lang(uage) example section, I would add a line > about how "Racket is many languages in one" (or similar), and then at > the end of the section add a blurb about how you can "make [your own] > languages". We will be adding something like that shortly. > I would add another link to the > Documentation section (or more likely point the "Documentation" link > again to the Software section so both are on screen together). If I can find a way to fit in a Docs link in the top bar, I will do that. That's probably worthwhile. -- 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.
