prev.rust-lang.org

Edit: Rust's website has an open-source license[3]. You can copy the code and use it directly! That's great news because they host it on S3 with Jekyll, which is ridiculously inexpensive. I'm not an expert or a designer. Your users will show you how to improve the design because you'll see evidence of where they're getting tripped up. For example, if a certain page is the last one most people see before leaving the site (other than front page), then you can tell that page A) solves a problem, or B) causes people to lose interest. A good starting point is to look at other language sites and decide which ones seem friendliest and least friction-y. How easy it is to get started? As examples, I really like Rust's website[1], and Elm[2] is pretty good, too. Rust's site is great because it's readable, all the important stuff is above the fold,

Hello everyone, As part of the current push to improve the Rust website [1], we are seeking input on what to include in the new and improved Frequently Asked Questions page [2]. If you have questions about Rust, suggestions for concepts that should be clarified via the FAQ, or any other ideas related to this issue, feel free to share them here. More specifically: - What questions do you or have you had about Rust? - What problems have you encountered during your experiences programming in Rust? - What topics or concepts in Rust do you feel deserve clarification? - Do you have any other ideas or comments about what the Frequently Asked Questions page on the Rust website should include? Thanks for any and all input you can offer! Each answer helps make the Rust learning experience better. [1]: https://github.com/rust-lang/rust-www/labels/RW