Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider creating an independent "Resources" website #614

Open
jvican opened this issue Mar 7, 2017 · 8 comments
Open

Consider creating an independent "Resources" website #614

jvican opened this issue Mar 7, 2017 · 8 comments

Comments

@jvican
Copy link
Member

jvican commented Mar 7, 2017

The Scala website has a section for learning resources: http://scala-lang.org/community/index.html#community-libraries-and-tools.

However, I think it deserves its own independent webpage. People visiting the website may miss "Community-Powered Learning Resources" and "Community Libraries and Tools". These actions have value on their own and they are actually quite critical for developers to know about.

What I propose is to have an independent page that we can use to let people know all the learning resources/tools they can use to code in Scala. That would include Scala Center's courses in Coursera as well as other ones (like the courses made by @MarkCLewis in this Scala Contributors thread). I'm sure we'll find more candidates.

We may also want to add more learning resouces, like Scala books, good blog articles (e.g. Li Haoyi's blog posts are great and very idiomatic), link to previous Scala Lang blog articles that are useful for learning, etc.

I would also like to add to the discussion my intention to create a section for people to get started in Scala. I'd like to have links to labelled issues in projects that people can work on. We could have community projects like the Scala Platform modules (better-files, json AST, possibly enumeratum), this website itself, sbt, and in general any other project that enjoys of maintainers that are eager to help and welcome new contributors.

The motivation of this last section is to let people get their hands dirty and hack on Scala from day one. I think it makes a difference having some guidance on far-reaching OSS projects that could motivate their learning experience while benefitting the whole Scala community.

What do you think @heathermiller @SethTisue @adriaanm @travis032654 ?

@adriaanm
Copy link
Contributor

adriaanm commented Mar 8, 2017

Yes! This is an important topic. What are website visitors looking for when they go to scala-lang?

Right now we break it down as:

  • documentation
  • download
  • community
  • contribute

You've identified two more important needs/interests:

  • learn (which is more than docs, it could be a course, a forum, a collection of blogs)
  • get involved

Here's another way to break it down (kind of according to increasing levels of experience):

  • get started (tutorial/tour, scalafiddle to try without downloading, first-timer install instructions)
  • download (returning customers who just want the bits)
  • docs (same as now, for quick reference: scaladocs, lang spec)
  • learning (if you want to deepen your knowledge, you wouldn't click on get started, and docs sounds too static)
  • get involved (combination of community + contribute)

@tpolecat
Copy link

tpolecat commented Mar 8, 2017

"Can you recommend learning resources?" is a very frequent question on Gitter, IRC, and Reddit, so 💯 for amplifying this part of the website.

@travissarles
Copy link
Contributor

What if "Getting Started" was on the learning page? I like to minimize the number of choices of things to click on. I think it makes it easier to navigate.

@MarkCLewis
Copy link

I like the idea of having this material under "Getting Started". I also think that it would be good to include information on each resource related to what background knowledge you need to have to make use of that resource. My videos and books would generally be for those with no background in programming or fairly limited experience. Many of the resources assume people have several years of development in Java or perhaps some other language. Trying to make that clear will go a long way to help people determine which resource is best for them.

Along those lines, saying what version of Scala it was created for could also be useful. This is a very dynamic ecosystem. That has many benefits, but a significant drawback is that resources can quickly become obsolete.

@jvican
Copy link
Member Author

jvican commented Mar 8, 2017

Many of the resources assume people have several years of development in Java or perhaps some other language. Trying to make that clear will go a long way to help people determine which resource is best for them.

Totally agreed.

Along those lines, saying what version of Scala it was created for could also be useful. This is a very dynamic ecosystem.

Good idea, we can also write a note that asks readers to report if material has become obsolete. I think that sometimes not even we know it is.

What if "Getting Started" was on the learning page? I like to minimize the number of choices of things to click on. I think it makes it easier to navigate.

Sure, this works for me. I would need to see the final look and structure of the website, though, because putting it everything into "Getting Started" would divert the focus of the sections. I would prefer short and accessible sections rather than long and detailed ones.

@travis032654 Would you be interested in getting a draft of all this?

@travissarles
Copy link
Contributor

Sure!

@jvican
Copy link
Member Author

jvican commented Jun 8, 2017

@travissarles Can you have a look at this any time soon? It would be great to have this and optimize for contributors 😄.

@xingyif
Copy link

xingyif commented Jun 24, 2018

FYI, scalabridge has a resources page that might be useful. It separates available resources by levels: Introductory, intermediate, and advanced, and also directly link to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants