scalatutorials / scalatutorials.github.io

7 stars 4 forks source link

Consider evolving to become a "platform" #2

Open oswaldo opened 11 years ago

oswaldo commented 11 years ago

As the last step in the interactive tour suggests that new steps could be collaborated to it, what about defining a standard modular way to do that? Sorry if it is already modelled to do that (didn't check source code yet).

The existing interactive tour could become one "Core Scala Tour" in a collection of tours where one could depend on another, like "Advanced Scala Collections" depending on "Core Scala Tour". This would enable a tree like structure to receive future tours.

Users could jump between different tours as they feel needed and at the end of a tour there could be suggestions for what's next.

After core, it could suggest the advanced or to a "Logging in Scala", so the thing could grow as a tree, encompass specific APIs (maybe API developers would love to have something interactive to show off their functionality).

This is a suggestion based on what I felt checking the existing tour, not really an issue (maybe could be broken in a few issues with the "enhancement" label). Anyway, keep up the great work.

eranation commented 11 years ago

Hi Love this idea, I thought of adding "levels" or "categories" to the existing single tour, but I think the approach of separate tour modules is probably better Would you like to join the effort? :)

On Mon, Aug 5, 2013 at 9:51 AM, oswaldo notifications@github.com wrote:

As the last step in the interactive tour suggests that new steps could be collaborated to it, what about defining a standard modular way to do that? Sorry if it is already modelled to do that (didn't check source code yet).

The existing interactive tour could become one "Core Scala Tour" in a collection of tours where one could depend on another, like "Advanced Scala Collections" depending on "Core Scala Tour". This would enable a tree like structure to receive future tours.

Users could jump between different tours as they feel needed and at the end of a tour there could be suggestions for what's next.

After core, it could suggest the advanced or to a "Logging in Scala", so the thing could grow as a tree, encompass specific APIs (maybe API developers would love to have something interactive to show off their functionality).

This is a suggestion based on what I felt checking the existing tour, not really an issue (maybe could be broken in a few issues with the "enhancement" label). Anyway, keep up the great work.

— Reply to this email directly or view it on GitHubhttps://github.com/scalatutorials/scalatutorials.github.io/issues/2 .