XBlock is the Open edX component architecture for building custom learning interactives.
The DoneXBlock lets a student confirm that they've finished an activity. The student can click through two states of the XBlock, shown below:
This can be useful for activities that are self directed or where completion is ambiguous.
You can see the DoneXBlock in action in the XBlock Workbench. Running the Workbench requires having docker running.
git clone git@github.com:openedx/DoneXBlock
virtualenv venv/DoneXBlock/
source venv/DoneXBlock/activate
make upgrade
make install
make dev.runYou can interact with the DoneXBlock in the Workbench by navigating to http://localhost:8000
For details regarding how to deploy this or any other XBlock in the lms instance, see the installing-the-xblock documentation.
If you're having trouble, we have discussion forums at https://discuss.openedx.org where you can connect with others in the community.
Our real-time conversations are on Slack. You can request a Slack invitation, then join our community Slack workspace.
For anything non-trivial, the best path is to open an issue in this repository with as many details about the issue you are facing as you can provide.
https://github.com/openedx/DoneXBlock/issues
For more information about these options, see the Getting Help page.
Details about how to become a contributor to the Open edX project may be found in the wiki at How to contribute
All community members should familarize themselves with the Open edX Code of Conduct.
The assigned maintainers for this component and other project details may be found in Backstage or groked from inspecting catalog-info.yaml.
Please do not report security issues in public. Please email security@openedx.org.
FutureLearn uses this kind of thing to great effect. Students can read text, watch videos, etc., and indicate when their done. This is convenient both for progress indication to the student (know what they've done, and for honor code grading (indicating to us that they believe they've finished an activity).
I copied some of the UX patterns from FutureLearn so that users of both platforms would have consistency of user experience between MOOCs. I didn't copy them exactly since I wanted to be unambiguously in the clear with IP issues around look-and-feel, and this was on a short anough timeline that I did not have a chance to reach out to FutureLearn for permission. As a footnote, this kind of collaboration between MOOC providers is probably worth pursuing -- it'd be to the benefit of learners on all platforms, and ultimately, the industry as a whole if we had consistency of experience between platforms where convenient.