v2.x: Semantics and structure

[lupomontero]

In line with this other issue, "Separación de retos, syllabus y agenda #534", now that we are splitting what we called courses into its constituent parts, it starts to look like the existing choice of wording may not be ideal. In fact, what was a course, is now four different things:

courses => topics + projects + rubric + agenda

In this context, I feel deeply tempted by a new metaphor:

Think of a bookshelf. Some books are fat, some are thin, the naming or topic selection might not be perfect, but it gives us (along with a bunch of metadata and indexing) the ability to use this collection of books on relevant topics, both as support/reference and discovery (free exploration).

Now picture yourself browsing the LMS, you have a link on the main menu (left hand column) that says "Library" or "Bookshelf". You click on it and you get a list of "Books", filterable by category (think JavaScript Core, Computer Science, Testing, Modules, Node.js, JavaScript in the browser, ...) and organised by a searchable tags. This would imply something like:

course => book unit => chapter part => part (stays the same)

One more thing, having a common bookshelf or library would mean that the same "content" is available to all cohorts, which is quite a bit different to the current setup, where each cohort has it's own version of the course. This is something that we will need to discuss in the context of the LMS/API too (knock knock @ivandevp, @FabianBravoA), as we'll need to come up with a solution (very short term).

Thoughts?

cc/ @chamodev @CaroLaboratoria @diegovelezg

[lupomontero]

@FabianBravoA: te he agregado como "assignee" ya que esta conversación va ligada al "rediseño" de la data y su representación en el LMS/API.