@pbteja1998 this looks nice, we should take this up as inspiration for our design.

The main problem we need to address with our learn guide interface is, atm we do not have much content per unit to display on the page. We only have a few concepts, one hyperlink to a video resource and one for a text resource recommendation per concept, and a few tasks to practice those concepts. The traditional left-hand / right-hand interface will end up making the page look empty.

One solution to this that we have internally discussed was, we can scrape the resources and display them on the page. So we would try to scrape the video and the text content per concept, and display them on the right hand interface when the user opens up a particular unit. This would fill up the page.

Question then is, to what extent can we scrape? What is the legality of that process?

And also keeping in mind that this would be a temporary fix, because where we eventually want to get is building a learning platform where any one can create learning modules for different topics, anyone can edit them, make changes and send changes back. Anyone can also pull different modules together to create their own custom guides. In this version, we expect users to produce content (Videos on YouTube / Text on our site, saved on our servers). We wouldn't then need to scrape anything, we will use the YouTube API to display the videos and pull the content from our servers.

So which way to go forward? Only based on that will we be able to make decisions on our design

Page after 'learn/subject' #66

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions