For "Contributing", would it make more sense to link to the official guide ( https://docs.racket-lang.org/racket-build-guide/contribute.html) rather than the blog post ( https://blog.racket-lang.org/2017/09/tutorial-contributing-to-racket.html)?
- The blog post is a little bit outdated on the "Hints for finding documentation" section (we now have a good way to locate where the doc is, thanks to Sam). - The blog post is probably never going to be updated, but the official guide can be updated. On Mon, Aug 17, 2020 at 5:45 AM Matthias Felleisen <[email protected]> wrote: > > > On Jun 21, 2019, at 6:15 PM, Matthias Felleisen <[email protected]> > wrote: > > Many thanks to all the people who sent feedback to the proposed new web > site. > > While, as you could see for yourself, the opinions are somewhat diverging > on many aspects, the exercise was extremely helpful. We will assess the > various ideas and see what can and cannot be implemented. If your idea > doesn’t make it, rest assured that it has influenced our thinking and your > effort of writing it down was worth it. > > — Matthias > > > > > Hi everyone, > > as you can see from the date of the quoted email, it has been a while > since we discussed the revision of our front page. And it is time to return > to this topic. The revised design is located here: > > https://users.cs.northwestern.edu/~robby/tmp/Web/www/ > > While some the feedback was contradictory, a lot of it was helpful and > found its way into the design in one way or another. Of course, that does > not mean everybody will be happy but the people who have spent a lot of > time on this effort are. > > We would appreciate the following: > > — test-drive the web site on your laptop browser to discover typos, > grammatical mistakes, bad images etc. > — also visit the page on your phones and see whether the phone layout > works for yours. > > Report problems/comments/suggestions to me so that the list doesn’t get > flooded. > > IF and that would be WONDERFUL, you have knowledge on how to improve the > CSS to fix a problem, create a pull request at > > https://github.com/racket/racket-lang-org/tree/wip-2nd > which is the relevant branch of the source of the Racket Lang Org web > site. > > We will go public in a week from today. > > Thank you all for all your inputs again and we’re looking forward to your > final comments. > > — Matthias > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-dev/E5F16FA3-F68B-4802-A9E9-1333B3A48014%40felleisen.org > <https://groups.google.com/d/msgid/racket-dev/E5F16FA3-F68B-4802-A9E9-1333B3A48014%40felleisen.org?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CADcuegv4Sn-8smJvKZB-1pxVM%2BcJ5jD%2BH7A509QTORTExNN%2BTQ%40mail.gmail.com.
