jtauber / learning-greek Goto Github PK

researching how to improve the way people learn Koine Greek

License: MIT License

Python 55.70% Makefile 1.14% CSS 26.95% HTML 16.09% Shell 0.12%

learning-greek's Introduction

learning-greek

I’m building this site partly to help people learn Koine Greek and partly to research how to improve the way people learn Koine Greek.

I’m bringing together lessons learnt from fields such as linguistics, learning sciences, psychometrics and machine learning, and such projects as MorphGNT, graded-reader, Quisition and Typewar. This project will combine many of my interests and endeavours from the last twenty years.

It will kick off with short surveys and games and will be built up incrementally with a strong focus on gathering data and performing learning experiments.

I’m starting small but have ambitious goals. I’m eventually going to need a lot of people to use the site to get the data I need. But I also want to teach a lot of people Koine Greek.

All the code will be open source and hopefully most of the content will be open as well. Data about individuals will not be public but data in the aggregate will be shared as potentially will de-personalized data.

Stay tuned.

learning-greek's People

Contributors

Stargazers

Watchers

Forkers

lucafavatella cloudxtreme classicist

learning-greek's Issues

trigger availability of some activities based on rules

Currently, the only thing triggering availability of an activity is the adoption-level / number-of-people-who've-already-done-it combo.

It would be nice if there were other rules for when an activity is available. Perhaps an activity is only available once another has been completed. Or done N times. Or based on the result of a survey question. Or when a particular ability with a concept is established.

The core should probably support all of these.

convert appropriate quizzes to "with answers" variety

indicate to a user how many times they've done a repeatable task

At present, you can't tell how many times you've done a repeatable task.

(note this is distinct from the case where we show total number of people who have done the activity in order to determine when it becomes available to people with an adoption level other than Bleeding Edge)

style new project like old one

staff dashboard with activity summaries

unique people who've done each activity
number of occurrences of each activity

better separate generic core from greek/site-specific stuff

At the very least separate packages but maybe eventually separate repos.

visually indicate different activity types

It might be worthwhile distinguishing different activity types such as a one off survey from a repeatable quiz. There are other dimensions to consider, though, such as the Likert-scale familiarity activities versus two-choice activities or the alphabet versus nouns.

I was considering using different background colors to indicate this (think Khan academy subject areas) but not sure which dimension(s) to capture.

The core should probably just support individual activities picking their category (so the activity authors determine the dimensions of classification) and this category then controls styling via CSS class.