Skip to content

Gather all content to be published on LearnOSM.org #9

Closed
lxbarth opened this Issue Dec 18, 2012 · 5 comments

3 participants

@lxbarth
lxbarth commented Dec 18, 2012

Gather all content to be published on LearnOSM.org and link it from here:

https://github.com/hotosm/learnosm/wiki/Content

@MappingKat
Humanitarian OpenStreetMap Team member

There are a few learning guides that are not complete and they will be put up asap. The quizzes, activities and handouts are not linked yet. Some of the quizzes might be converted to multiple choice questions so that it is more interactive to learn OSM.

One idea Kate and I had was that in order to get answers for quizzes, potential trainers or learners would have to log in a password. Thoughts? That way we can keep track of who is using the materials... ?

@lxbarth
lxbarth commented Dec 19, 2012

Thanks for the quick updates. Will take a look later in the day.

We don't have a straight forward way to do an authentication wall in this architecture.

@jeffhaack

We're very nearly finished with all the guides themselves - Beginner, Intermediate, Advanced, as well as slideshows, if we plan on keeping these on git as well. The canonical versions are all stored on Google docs, are you saying we should link to the relevant docs via the wiki here?

@MappingKat
Humanitarian OpenStreetMap Team member
@lxbarth
lxbarth commented Dec 20, 2012

@jeffhaack - not 100% sure I understand your question, but I'd love to have all content that is supposed to go up on the new learnosm.org linked from the corresponding pages on the Wiki: https://github.com/hotosm/learnosm/wiki/_pages

@jueyang is almost done with her first round of build out work on the site, my next action is to review the documents linked from the wiki and come up with a migration strategy to get them into markdown. If anyone's thought about this, I'd love to hear more over on #10.

@jeffhaack jeffhaack closed this Oct 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.