Contribute a module or lab to Risk Academy.
A module is written once, to one contract: the Academy’s course-kit schema, its lesson anatomy and its originality rules. It then passes automated checks, subject review and editorial review before it is published with its authors named.
- Course-kit schemara-course.v1
- Lesson anatomyTwelve parts
- Originality rulesFour checks
- Review stagesSix steps
- ProposeForm page
A proposal is not a commission
Every module is course-as-code.
Modules are written as course-kit sources (schema ra-course.v1). The validator reads the same file the Academy publishes, so what is reviewed is what learners see.
| Bagian | Apa yang dimuatnya | Wajib |
|---|---|---|
| Identitas | Schema version, slug, title, summary, programme and level (beginner, intermediate, expert or all levels) | Ya |
| Academic | Learning hours, delivery mode, audience, two or more learning outcomes with a Bloom level, and the assessment with weights | Ya |
| Ikhtisar | What the course or module covers and for whom, as content blocks | Ya |
| Modules and items | Lessons, quizzes, Lab and the practicum, each with an id and title | Ya |
| Bacaan | References with a citation, a link and the access (open, library or restricted) | In every lesson |
Alignment is enforced: every learning outcome is taught by at least one lesson and assessed by at least one quiz, assignment or lab.
What a lesson contains, in order.
The Academy’s editorial standard sets one anatomy for every lesson, so a learner always knows where they are.
Objectives, a hook and key terms
Lesson outcomes, a documented real situation that poses the problem, and four to six key terms.
Explanation, diagrams and a table
Why, how and what goes wrong, with at least two diagrams and one table, and a worked example with numbers labelled hypothetical unless documented.
Checks, a case and a lab
Two checks of understanding with answers revealed later, one documented case study, and an optional lab framed before and after.
Mistakes, practice, reflection, summary, reading
Common mistakes, how it works in practice, a reflection on the learner’s own context, a three-point summary and real sources.
Written fresh, cited properly, never copied.
The course kit checks what a machine can check; editors check the rest. The rules below are the kit’s originality guard.
| Aturan | Batas | Mengapa |
|---|---|---|
| No third-party name in a title | A standard, framework, product, platform or university name never names a course, module or lesson | Names belong to their owners. Cite them inside the lesson instead. |
| Short quotations only | At most 40 words in one quotation, and at most 2 in every 100 teaching words quoted, each with its source | Lessons teach in the Academy’s own words. |
| Point to sources, do not rebuild them | No more than two external clause numbers reproduced in one lesson | A reader is sent to the source; its structure is not copied. |
| No repeated text | A lesson shares at most 15 in 100 of its eight-word sequences with any other lesson | Catches templated or copied prose across the catalogue. |
Six stages before a learner sees it.
- 01
Usulan
The form below. You receive a reference.
- Dipegang oleh
- Labs intake
- Catatan
- Rujukan
- 02
Scope check
Matched to a planned course and discipline, or declined with a reason.
- Dipegang oleh
- Academy editors
- Catatan
- Catatan cakupan
- 03
Authoring
The module is written in the course kit, with sources and the worked example.
- Dipegang oleh
- Lab authors
- Catatan
- Course-kit source
- 04
Automated validation
Schema, outcome alignment, originality and repeated-text checks must pass.
- Dipegang oleh
- Course-kit validator
- Catatan
- Validation report
- 05
Subject and editorial review
A subject reviewer checks accuracy and sources; an editor checks teaching quality and the house rules.
- Dipegang oleh
- Reviewers and editors
- Catatan
- Review notes and responses
- 06
Publication and upkeep
Published in the course with authors and lab named, a licence and a DOI for its materials; corrections become new versions.
- Dipegang oleh
- Risk Academy
- Catatan
- Riwayat versi
Propose a module.
A working title, the discipline it serves, two to four outcomes and your key sources are enough to start.
- 01
Send the proposal
You receive a reference on screen and by email.
- 02
Scope check
We match it to a course or explain why not.
- 03
Authoring brief
The course-kit template and the review plan.
- 04
Review and publication
As set out above.
A proposal received is stored and queued for review; it is not a commission or an acceptance. Answers are handled under the privacy notice.
Questions about contributing a module.
Do I need to be in a partner lab?
Can I reuse my existing lecture notes?
Who is named on the module?
Is the module paid?
Kontribusikan bukti dari halaman ini.
Laporan is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- SurelGerbang GW-GCRIKirim dari halaman iniBukti, koreksi, kasus, metode, tinjauan, terjemahan, atau masukan profil. Kiriman tiba dengan label halaman ini, sehingga editor pemiliknya menerimanya.
- ZenodoDeposit terbukaDeposit dan ajukan ke komunitasTerbitkan catatan Anda sendiri di Zenodo dengan ORCID iD Anda, lalu ajukan ke komunitas Reports di sana. Kurator meninjaunya; DOI tetap milik Anda.
- LaporanGCRILihat semua cara berkontribusiJenis kontribusi, cara masing-masing ditinjau, kredit yang Anda terima, lisensinya, dan apa yang tidak pernah diterima.
Jangan pernah mengirim data pribadi, rincian infrastruktur sensitif, atau apa pun yang tidak berhak Anda bagikan. Kontribusi ditinjau sebelum digunakan. Mengirimkannya tidak memberikan hak kepenulisan atau editorial, dan sponsor tidak pernah membeli sebuah temuan.
More for authors.
Start with one module.
Propose it in a few lines. The scope check tells you where it fits and what the brief asks.