Ordering of Guides is suboptimal about docs.scala-lang HOT 2 CLOSED

While I agree that the ordering might not be completely optimal, I don't agree with the statement that all who go to the page implicitly assume that the guides are ordered in terms of increasing difficulty (level of user). User perception of the significance of the ordering of links on a page is entirely arbitrary.

Things are actually ordered by date of the document's completion. So, newer overviews will naturally appear on top. As we acquire more overviews (which we inevitably will, with the upcoming release of 2.10) I think it's pretty natural to place (and thus expect) new documents at the top of the list with one of these green labels that say "New" or something to that effect.

I also disagree that the list of subtopics contained within the collections overview is bad- it's such a high-demand document, that I think it greatly helps to have its contents displayed within the index page of overviews. It's a way of highlighting the document's contents (and importance), especially for people leisurely browsing, not necessarily specifically searching for details on the collections library. If such a user ever develops a question regarding collections, highlighting the document's contents on the overviews page might help one recall this document's existence.

Also, the entire overview section of the site is intended to be further filled. The idea was to have multiple "types" of overviews. The type "Core" was intended to cover overviews of essential libraries. I intended to create other sections as the need arose- for example, as concurrency libraries are developed, it'd be beneficial to have a section devoted to concurrency libraries (the Actors overview would naturally migrate there, once we have more concurrency overviews, which are planned.)

from docs.scala-lang.

I don't how what the order was in 2011, but the ordering at https://docs.scala-lang.org/overviews/index.html in 2018 looks decent to me

from docs.scala-lang.